Did anybody else find Waze super distracting? I tried it once around Seattle, on/off the freeway and there was just too much. Like, how can we add all the distraction of texting-and-driving, but into a navigation app. Bam! Here's Waze.
I couldn't help but think "Get all this stuff off my screen so I can see where I'm going" followed by "If I actually paid attention to or used this app it'd get me killed".
I'm sure if I'd stopped and played with the settings I could've got it to a manageable level but I really couldn't see the point. You're driving, the social aspect is a dangerous and unnecessary one. Just get me from Point A to B the best you can. Back to Google Maps.
I hate the interface, but I find that it does a better job of routing me around bad traffic than Google Maps does (even though it supposely takes Waze data into account), and MUCH better than Apple Maps. So I use it every day for my commute. I ignore the other crap and just pay attention to the route it is sending me on.
If I'm actually navigating to a place I don't know how to get to rather than commuting, I'll tend to use Google Maps instead. The display is much easier to read while I'm driving. And Waze's traffic avoidance routing is very aggressive, so it can sometimes suggest really stupid stuff. On my normal commute when I know all of the roads, I can easily tell it's trying to get me to do something stupid and ignore it. But in an area I don't know well, I'm more likely to unkowningly follow an illogical direction.
Holy hell, I was just lamenting Google Maps' lack of such a feature, and the range of commute time estimates being way too conservative. Lo and behold, they had the feature, it was just in Waze.
Thanks, that's a nice feature that makes it worth having on my phone. I'll still switch to google maps for the actual navigation because of the cleaner UI, but being able to look this up ahead of time is useful.
Yes! I recently used it for a road trip and was horrified at how much clutter and crap they put on the screen - it's like gamified navigation.
A great example - I really really don't need to know how many waze users are behind me, or driving the opposite direction, or hell - even in front of me. I also don't need 3-4 indicators on the screen showing the speed of traffic going the other way on the freeway. I only care about where I'm going and how quickly I can get there.
It literally is gamified navigation, you get point rewards for driving over "candy" on your route, although so many people use waze nowadays i only wind up with a piece of candy every few months.
FWIW the display of other Wazers is useful if you want to know the likelihood of any speed traps being correctly identified (a lot of other Wazers ahead of you in either direction should suffice).
Absolutely not. Waze is the pinnacle of GPS vehicle navigation apps. Google and Apple maps don't even come close.
Waze has probably saved me at least $1,000 in speeding fines, and has an almost uncanny ability to report upcoming hazards liked stopped cars or debris in the road. (Seriously, I can't believe how some car that just stopped is there)
Reading your comment is thoroughly confusing, since you really shouldn't be "looking" at waze while driving much since it talks to you the whole time. Adding an event is trivial, I mean I'm not sure how you could make it any more simple.
Unless you suffer from a specific condition preventing you from taking your eyes off a nearby screen I can't see how it would impact your driving any worse than any other GPS app
Is there some clever way of entering events better than touching the screen? I find that I often can't deal with the phone the second I see a hazard/construction/speed trap but would like to at least "register" it so I can send it off a few minutes later. Same for confirming alerts from others, I find that I can't verify an alert until I get to the ___location, and at that point I only have about 200 feet until the option goes away.
I defended Waze in this thread, but frankly it's absurd to me that someone would argue that a process which requires several taps on specific parts of the screen (like reporting a stopped car) is the same level of impact as other GPS apps that require literally zero interaction while you're driving...
I use Waze for nav and I don't find it any more/less distracting than Google or Apple Maps. I did turn off all sounds/alerts and never report on things while I'm driving. So basically I just use it for a nav app and nothing else.
The UX is goddamned terrible, and there needs to be a setting to mute alerts but allow turn by turn directions to be spoken. Why the hell I want to hear about every dead squirrel on the side of the road but NOT hear directions is beyond me.
You can turn off specific alerts (at least on the iPhone version); I've disabled "Hazards on shoulder" because it was getting annoying hearing it so frequently.
I'd make an exception for that. Though I don't find it to be all that useful. For one, I haven't been pulled over since I moved to CA 15 years ago and I speed EVERYWHERE. But I don't do anything else 'wrong' behind the wheel.
I use it as my navigation app. It works better when I got the bigger phone (Not sure how I used it on an iPhone 4s). There is a lot on the screen, but I usually just use the voice navigation feature.
It gives pretty good directions most of the time, and reroutes gracefully. Works in many countries.
I don't like the UI though. It figures out you've stopped and as I glance to see the map, an add pops up over the top of the screen, which is anoying. Clicking on the bar on the bottom of the screen to "stop" or enter a new address never seems intuitive. Its workable though and good at finding locations by name.
One feature it has thats nice, is that you can send someone your route, and it will when your about 2 minutes out (alternatively they can watch your progress).
It's fantastic for a passenger to help someone navigate with, but I could see it being distracting for an individual.
When you're a passenger, you can point out (and report) upcoming obstacles, amuse yourself looking at the little catcar bubbles, etc. They should probably make a quick "I am the driver/passenger" button, though.
Now that it is complete, I'd love to learn more about the work they had to do to port it over.
They've been talking about Waze for AA for over a year, so I'm guessing quite a bit of work had to be done to make this possible. In particular did they need to make any design changes to Waze to make it easier to use via the AA interface?
Unfortunately my 2016 vehicle only has mirrorlink v1.1+. Which unlike mirrorlink 1.0 doesn't actually mirror your phone, instead it is a proprietary app ecosystem with ten low quality paid for apps, even assuming any smartphone still supported mirrolink (which almost none do).
I wish there was just a single open standard in the vehicle industry. Toyota for example is refusing to do AA/Carplay and is starting yet another "standard" called SmartDeviceLink.
I'm disappointed Toyota went that route. When I was looking for a new car last year, CarPlay was a requirement so had to strike them off. Really wanted to buy another Prius too. It's also keeping me from going tesla too, I'd really love one but I just can't stand manufacturer developed entertainment systems. Ended up with a Passat that supports CarPlay, android auto and mirror link.
That's where Ford gets it right. They too are working on SmartDeviceLink, but also offer AA and Carplay so consumers have a choice. Toyota are currently offering nothing usable, and plan to one day only offer SmartDeviceLink.
I love Toyota's vehicles (reliability, looks, features, safety, etc). But when our Prius V gets replaced, we won't even consider Toyota as their infotainment units are antiquated, voice recognition terrible, and smartphone connectivity non-existent.
Toyota reminds me a lot of Nintendo, in the sense that neither company really grasps how consumer behaviour has changed with smartphones, digital services, and the cloud. Toyota are literally losing sales due to their obstinance on this, all to save a few dollars in navigation upgrades.
> I love Toyota's vehicles (reliability, looks, features, safety, etc). But when our Prius V gets replaced, we won't even consider Toyota as their infotainment units are antiquated, voice recognition terrible, and smartphone connectivity non-existent.
Have you ever considered getting an aftermarket infotainment unit? Choosing a car by infotainment seems like the tail wagging the dog.
I live in an apartment, still like the volt. 1) I grab free charging when I can, 2) it was an extremely cheap 3 year lease (even as a 15k mile a year lease)
> Unfortunately my 2016 vehicle only has mirrorlink v1.1+. Which unlike mirrorlink 1.0 doesn't actually mirror your phone, instead it is a proprietary app ecosystem with ten low quality paid for apps, even assuming any smartphone still supported mirrolink (which almost none do).
Both versions of the protocol stream apps rendered by the phone. v1.1 allows to create third party applications for it. Previously apps could be only provided by phone vendor. ML was never supposed to stream the screen of the phone constantly due to potential driver distraction. The devices that did this were probably uncertified and/or buggy.
> Toyota for example is refusing to do AA/Carplay and is starting yet another "standard" called SmartDeviceLink.
Well they do have a plenty of reason to not like AA/Carplay. Both give total control of head unit experience to Apple or Google. Which is a risky decision when you are dreaming about gradually moving from selling a product to providing related services.
> Both give total control of head unit experience to Apple or Google.
Which is to say they give total control to the device the user already has and uses everywhere else, so that they get a consistent experience. Anything the auto vendor provides will never be able to match that.
Yes, obviously. They both make head unit more appealing to the user. The cost for car vendors here is that they are suddenly dependent on a third party if they want to push any features on top of that experience.
First time using Apple CarPlay in Honda Civic 2017, and wow!
It's a annoying system at this point. Unless I want to use it as a glorified, big interface for podcast control, it is of no use to me. It cannot run mandatory apps like Google Maps, doesn't have Waze and I am not using Apple Maps.
Also, I cannot play the podcasts when I am using Google Maps for directions. The Maps app is unable to give voice directions, the podcast acts up and soon one or the other of them is stuck.
I gave up and just use a bluetooth based connection to run both of these apps at the same time.
I've got CarPlay in my 2016 Golf and it's useless. Why on earth I would want my car to take over the full functionality of my phone is beyond me. The only potential advantage would be running Apple Maps on my in-dash screen if I didn't have a Nav system already, but I do. And frankly, I'd rather just clip my phone to the dash than have all phone controls taken over by my car.
From the folks that use Android Auto with the car, many of the frustrations seem the same. It seems slightly better from a functionality standpoint, but less stable.
Waze may be the game changer. If only I could buy a cheap android phone and add it to my data plan without paying a ton of money extra each month...
So I have none of those frustrations as a 2016 GTI owner. Google Maps is wayyyy better than the built-in nav. If I searched for an address on my phone or even my laptop the address is already in my list of recent addresses in Maps and I don't have to even voice search for it. Although voice searching rocks and I dread having to enter an address in my wife's Odyssey nav interface through their knob interface. Then there is traffic routing which is also way better than what comes with the built-in nav. I can voice search and call a business from the same interface while I'm en-route as well.
I do wish that they would add the ability to have a real weather app in the ecosystem. After moving from the west coast to the midwest where they actually have real weather that can be spotty and fast moving it'd be really nice to be able to pull up an up-to-date weather radar view to see what's coming at me.
Now, there are the bugs....such as occasionally when I call someone it switches to the speaker on my phone vs. my car which is really annoying. It used to crash on a semi-occasional basis but I haven't seen that since I upgraded to a Pixel. Occasionally I do have to reboot the phone when it fails to connect. That is probably the most annoying one.
Huh. I really like the built-in nav. I particularly like having the turn-by-turn in the instrument cluster display, and the ETA across the top of the head unit screen, etc. Though as an iOS user I don't have the option of Google Maps anyway.
> Why on earth I would want my car to take over the full functionality of my phone is beyond me.
I've owned several cars thus far in my life, and so far, the functionality of every single head unit has been changed exactly zero times since the car left the line. When CDs became a thing, I had to add a CD player if I wanted to listen to them. When XM and Sirius came out, I had to add something to use them. Who knows what's going to come next? But if my phone is in the driver's seat, so to speak, then I can expect new updates just about every year now going forward, with new features coming this Fall with iOS 11. My 2017 Civic at least has a chance of being updated since the head unit runs Android underneath, but odds of Honda ever updating it are pretty slim.
My iPhone doesn't become a brick when I plug it in to my car. CarPlay is basically just a second screen - if I launch an app (while parked safely) that uses CarPlay, the dashboard comes to live with that view. If not, it sits at the home screen. But I can still use the phone however I'd like.
Stop the scaremongering and assumptions. Your jumping to conclusions does nobody any favors, and it ignores a whole host of safe and legal uses of a cell phone while it is plugged into a car.
I'm not sure how/why it would be required by law-- I could watch netflix on my cell phone while driving and have the audio stream over bluetooth if I wanted to; I don't see how CarPlay/AndroidAuto changes the legal framework here. I'm not saying you're wrong, I'm just not sure HOW. Could even just be something so simple as fear of liability I guess. But again, the bluetooth example comes to mind.
I tried to switch back this past fall when I moved to the city. I wanted to be able to get directions using Siri. I thought for sure they had worked out its kinks by end of 2016, years after its initial release.
I lasted less than a day. It had no idea where I was at times, even on major roads. It would more often tell me to turn after the turn than before it.
I don't know anyone who has used both Google Maps and Apple Maps who would call the latter "quite good", so I suppose it's relative. If all I knew were Apple Maps, I'd probably agree with you.
I refuse to use Apple Maps on principal. I prefer Waze, and use it. Yet when I click an address link, I get directed to reinstall the Maps app, and it won't let me open the links in the map of my choice.
I agree that it's virtually on feature parity and quality with Google Maps, including getting _really_ good at adjusting directions based upon traffic patterns in real-time...at least in the US. When I travel internationally, even in a big/populated locale like London, I just don't quite trust it just yet.
It's a shame, because on iOS Maps is a pretty polished product and the team deserves credit for where they've come.
Too bad Toyota is still putting frickin Entune in their cars with no Android Auto or CarPlay support.
I wouldn't be quite as annoyed by it if the damn navigation wasn't missing the address I need to enter damn near 50% of the time (in major cities too, in a 2016 model year car). One day I noticed they had a mobile app and assumed there'd be some easier way to enter navigation addresses from contacts, google maps, etc.. but no...its barely even functional.
But hey, I can check my stocks. so there's that?
Edit: I went on a little rant tangent there... Great work Waze team. I can't wait to be able to use this.
Mazda owner here. Still waiting for they mythical CarPlay/Android auto update that will supposedly come to 2014 and up models. They are using the same infotainment system in 2017 models so I'm still holding out hope.
I got to try out Android Auto on a rental Ford Focus last week and now I can't drive my 2015 Mazda 3 without hating it a little.
I'm sure you know that there is an unofficial Android Auto installation available on certain Mazda forums. Unfortunately, they still haven't managed to fix a serious issue with Bluetooth calling.
I used Mazda AIO Tweaks to get Android Auto support (along with other changes) in my 2017 Mazda 3. I am pretty sure they support older/other models as well. Very easy, took about 20 minutes from downloading to updating the car.
You can't do this any more if you're stuck with the very latest infotainment firmware version. It locks out the tweaks. Even if you don't have it yet, be careful because your dealer might "helpfully" install it on there for you when you come in for service or warranty work. Once this version is installed, you can't downgrade to the older tweakable versions. Very disappointing.
In addition, if they find you've tweaked the software, they won't honor any warranty claims concerning the infotainment system.
The idea alone that car companies would even try to provide their own navigation system that's built into the car is infuriating to me. I will have my car for way over ten years. By that time anything computer related that came with the car might as well have seen the thirty year war. In that same time I will have gone through three phones easily. The navigation and entertainment system needs to be as dumb as possible and as easily swapped out as possible. Anything else is ridiculous.
Don't forget the completely broken speech recognition.
I also love how, in our 2014 Prius V, if the Bluetooth gets disconnected and there's another device in range, it won't let me reconnect to the original device until the car is stopped and put into park... Because no vehicle has a front seat passenger?
I bought my Toyota for the motor, so I didn't pay a lot of attention at the time of purchase. I wish I had though. Entune is absolutely terrible. I'm still mind boggled that a quality manufacturer like Toyota would allow such a terrible piece of engineering in their vehicles.
Panasonic makes them, which made it click for me. Both Japanese companies, both titans. No betting on scrappy startups.
But I agree, I bought mine for the motor as well, and really that's what's important to me. Would I like a better head unit, sure, but I'd make the same choice again.
Don't feel too bad about this - Android Auto is nice, but it still has a lot of drawbacks and deficiencies. I just switched to a car without it and realized I don't miss it at all.
My 2016 Mercedes GLA was supposed to have support for Android Auto but the car arrived without it. Mercedes was working on the update for over a year now, and just few days ago I received an official reply from Mercedes Benz customer service saying that the technical department won't release such update, it was cancelled. It sucks to have such a modern car without support for it - and my partner's tiny volkswagen Polo supports both android auto and apple car play.
I am aware, but I really like having gps directions right in front of me on my screen in the gauge cluster. I'll probably figure out a dash mount solution at some point, but it would be so much nicer if everything just played nice together.
Since Android Auto runs on phones now, and it can be set to launch automatically when it connects to your car's bluetooth, I jerry-rigged a phone cradle that sits in front of my car's infotainment screen and mainly use that.
Yes, my 2017 Subaru Impreza has it. However I find it very clunky... the screen is not terribly responsive at all. Not sure if its my phone (an aging iPhone 6), firmware in the head unit that can be fixed, or a poorly engineered hardware in the head unit.
Thankfully Apple has disabled the ability to do that in iOS 11 - all apps have to have the “only when using” option. Hopefully google will follow suit with Android soon.
I'd prefer they give you a choice, but a big part of the Waze concept was that it was a social thing - you keep it on while driving so other people on the same road know how much traffic there is, you report hazards, etc. If you only use it when you are actively navigating then you aren't a true member of their community. (Note that I'm not advocating here one way or the other, just explaining their concept. I'm well aware of the privacy issues.)
Perhaps, but it absolutely wrecked my battery life when I didn't kill the Waze app the other day after arriving at my destination. I wasn't moving, but my battery went from ~90% to ~40% in the span of a movie: in my pocket, with the display off.
I care very slightly about the privacy implications (I'm already letting them track me sometimes so I can't be that concerned). What bothers me is that it continued to drain my battery to the point that my phone would have been dead before I got back to my car to head home.
I used Waze during my commute a couple months ago. I didn't look at my phone before lunch. When I went to look up what food was in my area that day my phone was already prompting for low power mode. Plugged in to my car my phone battery only maintains charge with Waze running.
Google/Apple maps do not seem to have this problem.
Yeah my issue was that it was originally able to be set to "only while using", which they disabled without notice. All of a sudden my ___location was being shared 24/7 without any warning or permission.
I don't mind contributing ___location data to the betterment of the app, it more comes down to a battery life and transparency issue.
Not that it applies to Waze, but Apple's entire ___location permission stack is hot garbage.
Most notably: Literally everything about dealing with significant ___location changes when in the background/app is suspended. That entire dev team has some bad karma coming its way.
Agreed. I find Waze has more aggressive rerouting. Maps tends to stick to simple navs at the expensive of a few minutes. Waze will zig-zag me around town. I do find both apps make my phone hot and gulp battery though.
Waze has rerouted me around catestrophic traffic jams multiple times, both cases having a companion launch apple/google maps and they were more than happy to send me right through it.
The routing algorithms are completely different, as well as the map data itself. Waze allows users to edit the map, whereas Google Maps no longer does. Google Maps only allows users to submit/edit _locations on the map_. They do share traffic and accident data, but that's about all.
In my use case, stop light cameras and speed cameras positions. There is an obnoxious grid around DC/Maryland that costs me around $300/year in tickets. To the "why don't you go slower then" crowd - believe it or not, I drive carefully. Aside of the eventual speeding, silly situations like being half-way on the wrong lane while passing a green light can cost you $150 here.
> silly situations like being half-way on the wrong lane while passing a green light
You're not supposed to change lanes in an intersection. It's confusing to people trying to turn and figure out what lane you're in. This is why they fine that activity.
Not the gp, but there are situations where that kind of activity is absolutely necessary. Think about driving behind an Uber that stops in the right lane immediately after clearing the intersection, then puts their hazard lights on to wait for a passenger. Your options are either (1) stop behind the Uber, potentially blocking the crosswalk and the intersection when the light changes, or (2) make a lane change in the middle of the intersection and pass the stopped Uber.
I thought this scenario is about changing lanes within the intersection, as opposed to just outside of it where you could potentially block the crosswalk?
If I had enough space to get into the crosswalk, I'd do so to hopefully nudge the Uber along where I can safely make a lane change on the actual street. If the Uber doesn't get nudged along and there's no other legal way to move... then I'm "stuck in traffic" quite literally.
It's not absolutely necessary to avoid traffic by breaking traffic laws.
In the DC metro area, lots of times traffic is created by exactly the same scenario. I don't feel bad about it; the root cause was the Uber driver or more traffic up ahead combined with the limitations of human response time.
If you're following at a distance, you might see the Uber stop before you enter the crosswalk. The problem with nudging into the crosswalk is that when the light changes, you're now forcing pedestrians out into the lanes which increases the chances that they get hit by a car.
Blocking the crosswalk is also a traffic violation. In the Uber scenario I presented, it's really not a question about if you want to break a law, it's which law would you rather break.
Your mileage may vary though depending on your legal jurisdiction, but lawmakers generally do not write 'average' laws to be unreasonable in eyes of the average person.
What is "supposed" to happen in lawmakers eyes, is that traffic grinds to a halt. Pedestrians stop crossing the road at that particular point and thus don't get hit by cars, and either the Uber driver intentionally causing all these hardships moves or gets ticketed.
Unless crossing the road, or moving around traffic is a matter of life or death ... no one is supposed to break the law and everyone is supposed to be temporarily inconvenienced. Just because someone else broke the law doesn't give the next people rights to break the law in order to ease their convenience.
Do you really think that exception would allow a driver to avoid a fine? Without going to traffic court and discovering that the judge is a close relative?
The California vehicle code does not prohibit changing lanes in an intersection. Laws may vary in other jurisdictions, but here it's fine unless the lane change is unsafe for other reasons.
If you don't care enough to slow down then I don't know why you'd bother evading speed cameras, and if you do care, slowing down is probably a smarter option.
Waze allows using the phone speaker for nav directions, even when connected over bluetooth. Google maps doesn't have this option. My cars bluetooth won't autoswitch over to the nav bluetooth audio when directions are coming in when listening to another source.
If you know the area, know where you are going, know when the nav is giving you a bad route, Waze is much better. It optimizes your commute time so that you can avoid traffic hot-spots. Save a couple minutes here, a couple there, it adds up. You just have to know that "yeah, that road seems quicker, but you always get stuck at the light".
If you don't know where you are going or are traveling long distances, Google Maps is better. Waze simply can't handle long distance routes very well and Google Maps is far less likely to send you down some weird road to avoid a hot-spot. You definitely want to try and avoid weird roads or odd routes in strange areas.
It might be because I am used to it but I find Waze interface better overall. For example, selecting alternative route is not that obvious on Google map for long distance travel, it is a single click on Waze.
Waze uses a completely different pathing algorithm, and it's straight-up worse than Google.
The way Waze works is that it will do everything and anything it can to avoid a busy intersection or a congested street, without regard to whether or not going out of your way will take more time than just slogging through the intersection or the street. Waze will prefer a route that takes an hour but only takes streets that are empty over a route that takes half an hour but involves multiple busy intersections. Google optimizes its routes purely by time: whatever route will get you there the fastest is what it'll go with.
Waze also has a notorious tendency to encourage people to make left turns from the right lane and vice versa. It's illegal and dangerous. These instructions often take the format of "turn right on [six-lane arterial] and then immediately take the next left", even though it's physically impossible to get across the street in time.
Waze also cannot recognize the entrance to my townhouse complex as an entrance. It will always suggest cutting through a neighboring gated community to get to where I live. As a frequent Lyft rider, this means that I cannot ride with any driver who uses Waze if I'm going to or from my home.
I often have to call drivers who pick me up from my house and say "please confirm that you are not using Waze", and if they say they're using Waze, I will immediately cancel. If they're close enough though, I'll just monitor their route, and I'll immediately cancel if they take a route that only Waze will suggest (for example: the entrance to my complex and the neighboring gated community are on separate but perpendicular arterials; if they're driving on the arterial my entrance is on, but they drive past my entrance and then make a left turn on the other arterial, I'll know they're a Waze user, and I will cancel).
Sometimes, when I'm being picked up from work, I'll see a driver starting up Waze, and I'll say "please don't use Waze; it can't get to where I'm going". Sometimes, the driver will let me manually navigate them or on rare occasion even start up Google Maps, but I've also experienced a bunch of drivers who will throw angry temper tantrums because I asked them politely to not use Waze. One driver started screaming her head off at me while punching the steering wheel. I've had to get out of the car and call their trust & safety hotline a couple of times. I'm convinced that these drivers know that Waze will suggest routes that take more time than Google does, and that they are deliberately using Waze to run up the meter and make more money; as such, they get pissed off when a rider won't play along.
I've been beta testing this on my Ford Focus with Android Auto. It's a nice system, but it does make me wish that they made a screenless little android auto device I can leave in the glove box so that I don't have to go through the hassle of plugging my phone all the time and going through the whole dance.
I tend to need to charge my phone anyway but for short trips sometimes I don't even bother launching AA, which is a shame.
Waze has been pretty good though and it works well in the AA environment, which is purposely limited so you can't get into to much of a distracting flow.
What exactly do you mean by "the whole dance"? I've found Android Auto to be pretty simple to use. There's just one short USB cord I plug in right next to my shifter and I'm done. Everything comes up automatically. This is on a VW Golf, so maybe it's simpler than it is for you in the Focus?
Most of the problems I've had have been software bugs. Like this morning when I attempted to send a Hangouts message. The assistant voice made it sound like it worked, but nothing every actually sent.
Anyway, I'm not sure a screenless device is really what you want. Most of the appeal of AA is that it uses your regular phone, so it can use your data, read and send message, make calls, etc.
I left more specific feedback in another part of this thread.
With regard to the screenless device, I do like having my phone be the centralized device of the entire thing, I just would like to make it a more permanent part of the car so I can just hop in and drive.
I am debating trying a spare SIM and an old device and just leaving it in there plugged all the time, but that just introduces an entirely different set of problems.
Curious - what is the 'dance' that's required beyond just plugging the phone in? Seems that needing to do anything more than that is bad design on either Android's part or Ford's.
It is a combination of bad design by both parties and initial setup hassle. I'll try to document what it's like to leave my driveway. After the initial setup, bluetooth pairing, making it a trusted device, etc.
- Start car.
- I can't plug the phone in right away, because it will miss some kind of internal step, I have to wait for Ford Sync to finish "booting", then plug in my phone and stow it the box where my USB plug is.
- Android Auto then launches, unless another app on your phone is prompting you, at which point nothing will happen, you have to dig the phone back out to find out what happened.
- AA launches, click mic button on wheel (it's a hw equivalent of ok google): "Play Metallica." Always launch music first because if I launch nav first and then want to play music, it will switch off the map and show you the music controls, which I only want when I'm not navigating. But if you launch them in the right order you'll get nice music notifications on the map.
- Click mic button on wheel: "Navigate to whereever", unless of course I don't know where I am going, but if I was clever enough to put the address in my gcal it will already show up on my auto's screen, this is my favorite feature of AA. If I don't know where I am going I need to look it up on my phone, so dig it out, and then the AA app fullscreens a splash screen on the phone, so I need to drag down the notification bar, unfullscreen it, use my phone, relaunch AA again (or just unplug the phone and plug it back in) then stow the phone.
- If I put the car in reverse before this the rear backup camera turns on so I can't access the UI at all, so I might have to do steps some of the steps again depending on when I put the car in reverse and if the car was listening.
- Car now moves away from house and kicks over from Wifi to LTE and most of the time this works, but occasionally the music will just stop playing so I have to click on the "play" button again the UI.
If I'm unlucky Ford Sync will notice that something stopped playing so it will automatically put on the next music source, FM radio. Now there's no way for me to get back into Android Auto without unplugging the phone and plugging it back in. Sometimes(?) there's an android auto icon that shows up in Sync that lets me back in but I haven't determined why sometimes it shows up and sometimes it doesn't.
It's not a bad system, it's just still 1.0ish; once you're past all this crap and on the road it's really nice to have all my music and maps available, and of course having the google assistant is much nicer than I anticipated, so I can do things like "good morning" via a voice command and it will play my daily summary.
I can echo a similar scenario as above. While plugging in my phone to Android Auto is easy, there is still the time required to allow your phone to transition from WiFi to LTE, back-up-camera enabled when backing out of your garage, and opening up the Android Auto menu (but first I have to tap home and go into it).
Overall, in a driving commute of about 25 minutes I have to spend the first 2-4 minutes effectively waiting to configure Android Auto and for it to kick in with the proper signal and menus.
It's a hassle for everyday commuting when the purpose of AA is to simplify a lot of the work. The menu systems are also a bit of a pain to navigate for podcasts. So I end up organizing my music/podcasts before I get in the car.
>While plugging in my phone to Android Auto is easy, there is still the time required to allow your phone to transition from WiFi to LTE
Tip: open the Android Auto app on your phone while you're unplugged, go to the settings menu, and choose the "Limit WiFi" option.
This way it'll just outright disable WiFi when Android Auto is engaged, so you don't have to wait for it to realize you've driven away from your network.
Maybe it's not due to AA but Ford Sync.
As far as I know, I only needs to connect my phone using USB regardless of whether the car is powered up or not.
I agree, it is probably the OEM implementation. I have used both Carplay and Android Auto with an aftermarket Pioneer head unit and the phone can be plugged in before the car is turned on.
Okay, I have shared at least one of those problems (the backup camera taking over, although I think I can just close out of it on my VW). I also get a weird intermittent problem where my phone will freak out and my car will stop recognizing it for a day. Not really sure what component is at fault there (phone, AA, or car).
I also have the Wi-Fi problem. I'm not sure why AA doesn't automatically just turn it off when it starts. I've been meaning to create a Tasker profile to do that for me.
I use Waze daily to get to work and get back to home. Europe is full with speed traps and total unexpected speed limits. For me Waze is a must have app every time I go somewhere with the car.
I can't say I would ditch my iPhone just because of this (or maybe I would?), but I might get an android phone just to use it with Waze in my car if this really works great...
Apple CarPlay is total useless so far, even to play music from my iPhone in the car, I rather use the built in media app from VW. Apple maps in Europe is a total joke. Many times it tells me I should drive into a one way street or it would try to take me into pedestrian zones...
I hadn't used Waze in a while but used it twice in the last month. Seems like no one uses it anymore, and it was 2/2 in leading me down a bad, more time consuming path.
I very rarely take Waze's advice about alternate routes after being burned a few times, and I have learned to expect that it's ETA prediction will always be optimistic by about 15-20 minutes in my case. I mostly use it to pick between a few well-known ways to/from work and to get more traffic data than Google Maps will show.
The most infuriating thing about Waze is when you hit traffic that it already knew about but only then does it add 5-10 minutes in delay time.
Last I used it was a good four years back and it tried to make me take left turns from a small alley into a major high at during rush hour in la. Ended up costing me more time than if I just hopped on the main road to begin with.
Google Maps has gotten pretty obnoxious about this lately too.
LA rush hour is bad enough with crowded enough side streets now that the way to outsmart it in my experience is to be dumber than Google and just take the damn highway after all, with the exception of a few certain areas (like "the highway's moving ok overall but the exit I need will be backed up an extra five minutes so I'm going to got off early" type stuff).
Actually just got bit by this this morning. Google said to take 405 - sepulveda because there was "no traffic" towards lax. Turns out that's because sepulveda was basically closed for road work. Ended up almost an hour later than I planned.
I had completely different experience. We would have been stuck in traffic for 30-45 mins had we followed Google Maps, but using waze's alternate route we passed through it in 10 mins.
Should I be seeing an update for Waze in the Play store? It says I am up-to-date but I did not have the option to use Waze when I used Android Auto just a couple of hours ago.
Was trying to figure this out myself. After looking at the Car Play website, it doesn't seem like they do, which is annoying.
I'm assuming that Apple isn't playing nice with Google and giving users free choice about which nav apps they can use and that Google would release a Google Maps and/or Waze version for Car Play if given the ability.
Again, these are assumptions, if anybody can correct me on that, I'd love to hear otherwise.
This to me is a big enough deal that I would seriously consider an Android over an iPhone for this reason alone. I never use Apple Maps, it's an inferior product on every level, and I can't understand why Apple seems insistent on the idea that people want to use it. In my experience the only people who use Apple Maps are those who are too lazy to change from the default nav system built into the iPhone or just don't care enough to use a better nav system. It's never people who actively prefer Apple Maps.
Google Play Music works just fine in CarPlay, but currently Apple only allows music and messaging apps. We don't know why Apple doesn't't allow navigation apps but its not because they are pushing Google out.
> In my experience the only people who use Apple Maps are those who are too lazy to change from the default nav system built into the iPhone or just don't care enough to use a better nav system.
Luckily, iOS 11 has brought / is bringing lane-guidance to Apple maps. This is a huge deal for me and makes maps.app a lot more tolerable and driver-friendly.
After the last decade-plus of having car companies try to force you to buy their updated maps, I refuse to buy another car that doesn't include CarPlay support.
I rented a car with CarPlay a couple of months ago and I was surprised at how easy it was to just plug my phone in and get going with it.
in a dense urban environment, like where i live, waze significantly out performs google maps on a day to day basis. its routing is much better for real time issues and is very quick to react to things happening on the road, including cops, stopped cars, hazards, etc. when i am doing less serious driving (i.e., outside of commuting or running late), my car's navigation or google maps works fine.
Waze always baffled me. No one I know uses it and most never heard of it. Google had pretty sophisticated data/algo of their own when they paid $1+B for this thing. ELI5 - why should any one care about Waze?
Waze's primary innovation was to crowdsource near-realtime traffic information. They weren't the first[1], but they were the first to do it on a large scale. Some of it is automatic (e.g. speed, which usually reflects traffic conditions) and some of it is interactive, encouraging users with "points" to fumble with their phones in order to report police sightings, road obstructions, etc.
> No one I know uses it and most never heard of it.
Intersting — everyone uses it in California, to the point that it strongly affects traffic patterns[2]. Where are you?
I'm in Palo Alto and actually had seen their small office on Hamilton. I do know how it works and tried to myself but found it really cumbersome. The only explanation I can see is iPhone users who didn't have the benefit of Google maps a few years back that propelled Waze's use. As for the valuation - if they had even 10M active users, Google paid $100 for each of them, knowing that it was inevitable that they'll eventually get the iPhone users anyways.
Waze is great for commutes or other local driving you don't normally need nav for because the traffic routing is top notch (I've had experiences where it has told me to exit highway immediately and easily saved me an hour because of a terrible wreck that just happened). Also great for identifying speed traps on the highway which is why it's really popular with truckers.
It has international appeal as well, the map editing feature has made it a hit in places with less than perfect map data:
My kids played with it a few times on long drive to tell me where he spotted the police car(s), accidents, etc.
Kind of fun thing for your kids to do on a long drive. That might be why the cartoon like interface.
Like Pokemon Go, the constant network traffic + GUI interaction makes it huge battery drain. I deleted the app from my phone.
Google map's traffic info is very good. I suspect Google paid that much likely because potentially FB, MSFT or Amazon "might" get it and use it is a beach head to enter the Mobile Map App market. If that's the case, it is a very good play on Waze's part to get the high valuation.
>My kids played with it a few times on long drive to tell me where he spotted the police car(s)
There's something seriously wrong with society when both kids and their parents are working together to evade the police, and obviously have no respect for the police. And the problem isn't with the kids or their parents. Average citizens should not see their police as an enemy group generally working against their best interests.
I couldn't help but think "Get all this stuff off my screen so I can see where I'm going" followed by "If I actually paid attention to or used this app it'd get me killed".
I'm sure if I'd stopped and played with the settings I could've got it to a manageable level but I really couldn't see the point. You're driving, the social aspect is a dangerous and unnecessary one. Just get me from Point A to B the best you can. Back to Google Maps.