I have big time trouble connecting my A12 Android Auto to my brand new BMW iX3. My Oneplus Nord connects flawlessly, the A12 does not. On Samsungs website I read that Norway is not among the countries allowing Android Auto (https://www.samsung.com/ie/support/...fficulty-connecting-to-or-using-android-auto/), could that the reason?
I cannot believe that.
I live in the Netherlands and we are also not in the list and we can use AA without any problem, but, your phone AND carsystem will have to connect with each other.
It sounds more that your A12 does not have the right software for it.
Go to apkmirror site and download the AA software and install on your phone.
I have downloaded the latest version from Google Play, isn't that version as good as the apkmirror-versions? My A12 connects OK with the car when it comes to hand free phone operations over Bluetooth, but when trying to establish AA, the car says "The connection failed. Check both the Bluetooth and WLAN settings on the mobile unit". Both BT and WLAN are active on the phone, and during the process an AA logo splashes on the mobile screen.
Edit: I have downloaded and installed Android Auto 6.8.613323 which I suppose is the lastest release. Same result
Ah, now i get it.
I had a Nokia 7plus and my radio-unit worked, This summer i switched to a new Nokia X20 phone, and had the same error.
After switching the car-cable with the cable that came with the new Nokia, it suddenly worked.
So try to use the cable that came with the new phone, instead of the old cable from the previous phone.
Thanx for the tip, elot01! I switched the cable to the one that came along the A12, but nothing happens when connected to the car USB except from battery charging and the option to transfer files. I am in contact with Samsung support, and so far they have been helpful. But they have not been able to solve my problem yet.
Once they have, I will post the solution here. But any tip for the forum community is highly welcome.
Samsung has given up and redirected med to Google since "this is a 3rd party SW". I haven't managed to find any Google support center to contact, but I have figured out the problem myself.
I want to have a wireless AA, and it seems like this is only supprted with handsets capable of dual band wifi, ie. 2.4 and 5GHz. The Samsung Galaxy A12 only support single band (2.4GHz).
So there goes my A12 back in its box to be placed in some drawer and forgotten. A low-priced telephone, but still a waste of money
A tip to Google/Samsung: Why not display a message saying "Android Auto is only supported on dual band wifi mobiles" when only 2.4GHz is supported?
If you want wireless, also take a look at Carsifi (still in Kickstarter) or AAWireless (former kickstarter).
Then you don't need a new phone
elot01 said:
If you want wireless, also take a look at Carsifi (still in Kickstarter) or AAWireless (former kickstarter).
Then you don't need a new phone
Click to expand...
Click to collapse
If you want a dongle slamming aroud in you car occupying one USB-port this solution is probably OK. But it's much easier to spend the 85$ extra on a mobile with dual-band wifi.
Related
Hi, I just recently got a new Golf with the app connect system that has Android Auto functionality built in. However, I just can't get it to work with my G4. I've downloaded the Android Auto app, I've tried using different cables but every time I plug it in the AA app seems to just crash. It also won't connect manually when I try to connect it in the car. I live in Australia. Is there anything else I can do/download to make this work? Thanks.
Don't know if this will help, but try to set the Android Auto on a headunit. Mine was set to Mirrorlink by default.
Maybe in the settings you should define it to choose Android Auto instead ?
Make sure the phone is unlocked when its plugged in. Also, try plugging in the phone before you turn on the car. My Nexus 5 is able to connect 90% of time on my 2016 GTI.
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
monkadelicd said:
I just picked up my GTI last night. The salesman couldn't get Android Auto to connect to my AT&T G4. Android Auto was set as the preferred connection. I've tried connecting with my phone locked, unlocked, plugged in before/after the car is on, plugged in after/before the phone is unlocked, USB debugging on and off, MTP, charging only, PTP.
Click to expand...
Click to collapse
Did you ever get connected?
Robbie Doo said:
Did you ever get connected?
Click to expand...
Click to collapse
tt
I work at a vw/Skoda dealership. I am tech savvy. I have tried I phones and various Androids with Mirrorlink/Android Auto and to be honest the results are pretty Mixed. I phones mostly pair OK but with so many iterations of Android topped with manufactures bloatware its impossible. I have failed to pair phones that are compatible and tried every app every cable and every configuration even the Manufacturers are clueless. Some models I managed to pair took me 40 or 50 attemps. Android Auto is in its infancy and stability will take time. I managed an S5 with ease and S6 with great difficulty a HTC one A9 which is very unstable. A HTC one M8, but didn't manage the Huawei P8 yet but I'm working on it. I failed with a galaxy S4 and succeeded with another one. I have an LG G4 on the way so that will be interesting. I have had 100% success pairing I iPhones but customers tell us the connection drops out. However I do think Android Auto offers more in terms of functionality if you can live with the fact that you may not ever get it working.
Anything new with G4
Did you manage to make the LG G4 working?
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Konstigt said:
Hello
I had the same problem with my VW Passat GTE 2016 + LG G4. Solved it by going into the settings in the car (under App Connect) and chose Android Auto as default instead of MirrorLink which was the default before.
(although it doesn't work very well anyway, sometimes it does, sometimes it doesn't)
I have Android Auto 1.6.2400
Click to expand...
Click to collapse
Just to confuse the issue even more, my vw connects to android auto pretty much perfectly every time & yet I only discovered by accident that the default setting on the head unit was set to mirror link so maybe that's not the cause for you after all. It's pretty basic software so far it seems.
Sent from my Nexus 6P using XDA-Developers mobile app
I picked up my new Golf today, but it doesn't have the App Connect. My phone is an Oneplus One with MM Cos 13, do you think Android Auto can work with it?
Just my experience : I own a 2016 Jetta with App Connect and a Nexus 4. I had similar issues with AA connections first. The phone was running Android L 5.1..1. 2 weeks ago I went ahead and installed CM13 and now AA works way better : I never had a connection failure since... Really a plug and forget experience now. So I think Android M is better for Android Auto. Moreover I read that latest AA update includes fixes for connection stability.
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
AA is buggy but I'd have to say......
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I think this is your radio hardware and not the AA app. But you never really disclosed what phone you are using and if it has been modified or what so there is no clear help answer that I can assist you with.
hi, i've got the Note 3 (SM-N9005) running stock lollipop 5.0 (baseband N9005XXUGBOI2). my phone was previously running 4.4.2 kitkat with root.
the connection is very hit and miss. it will keep trying to read my phone when plugged to the car and the phone will keep shifting between "connected as a media device" or "connected as a USB accessory". When its connected as usb accessory, the phone screen will black out for a second and then goes back into the previous screen which is usually home page of the launcher. i think the "blackout" might be the phone trying to boot or load android auto app but gets disconnected as it tries to get in.
i have to plug the usb in and out a few times and sometimes by lottery, it will establish a successful connection and AA loads on the car screen. i've found that if i open the app first on the phone and then plug in the usb, it will have higher chance of getting a successful handshake.
hope this makes sense.
I have the exact same issue: VW App-Connect in a new 2016 vehicle with a Galaxy S5 running Lollipop. Very annoying because once the two are connected it does work reasonably well.
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I believe Verizon phones were having USB connection issues because of some special app they had that did stuff over USB, and an update fixed it.
Some USB connection issues can be solved by changing the mode of USB: MTP, Charge Only, etc.
Some issues can be worked around by enabling (or disabling) USB debugging. This is under Developer settings after Dev mode is entered by tapping Build number 7 times.
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
I have similar issues with my 2016 Skoda Fabia Combi. I'm guessing the infotainment system in the Skoda is pretty much the same as in the Volkswagen. Many parts are because Skoda is owned by VW. After tons of trial and error, I've had some success connecting my LG G3 but first let me tell you how I ended up in the current situation.
I have tried to connect thee different android devices (LG G3, HTC One M7 and Nexus 7 tablet all running Lollipop) with bunch of different USB cables. The result is always the same. On the phone I see black screen flashing before it returns to home screen and nothing else happens. From the recent apps view I can see that the black screen was AA trying to launch. CarPlay with iPhone works fine.
I live in Finland so I have sideloaded the AA app and at first I thought that the issue is caused by AA not being officially available here yet. After searching this forum and other android forums I found out that other people are having the same issues in countries where AA is supported so maybe this is not the case. Obviously it's not also a device problem because I get exactly same results with different devices from different manufacturers. Only common nominator seems to be the VW/Skoda infotainment system? Correct me if I'm wrong here..
In the Skoda smartlink menu you can choose your preferred connection protocol from Android Auto and Mirrorlink. This affects the order the car attempts to establish the connection. I read from a Skoda forum that someone had a successful connection after he had changed these options around so I tried it. I checked Mirrorlink as a preferred method and tried the connection: no luck. I changed back to AA as preferred method and to my amazement after this the AA launched on the phone and I had a successful connection! If the VW has similar option I suggest you VW guys also try this.
My current situation is that most of the time the phone does not connect at first try but after changing the preferred method around it does. I have also other issues with AA. After connecting I cannot adjust the volume first from steering wheel/stereo volume knob. Spotify audio goes to a wrong channel at first (I can hear it only when i activate voice command) After changing music app to Google Play Music and then back to Spotify it starts working normally and I can also adjust volume. And of course the restriction on browsing your Spotify library. It is the most stupid thing I've ever seen at that level of software development.
rafalucas said:
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
Click to expand...
Click to collapse
Auto dealers tend to know almost nothing about software and smartphones. They know how to sell cars, and the mechanics tend to know how to fix them mechanically, more or less.
And they can almost always say that there is likely an update due at some point.
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
If you get it working you can get a better idea if your car HU is at fault.
I wonder if there are car stereo shops where you can plug your phone into a Pioneer AA unit, like 4100NEX, and see if it works OK on that.
I've had my 2015 Seat Leon (also VW group) for four months now and also having trouble with Android Auto through the SEAT 'Full Link' connection. It seems to be russian roulette whether it'll make a connection and start AA when you plug it in. Sometimes you'll get a 'Connection failed' message, other times you will see the system try AA, fail, then try MirrorLink then fail on that too (as my Nexus 5 doesn't support MirrorLink). As others have said you see the phone screen go black then crash out and goes back to the home screen.
The only solution I have is to restart my phone and try again. Its almost my routine now to restart my phone just before I know I'm about to go for a drive. It beats having to sit in the car watching my phone reboot before I set off!
I didn't know you can change the USB settings on the phone, so I'm going to go through the various settings in developer options to see if any of these help. I'm thinking 'Charge only' might be useful, unless AA needs MTP or network connection to operate?
seems like i'm not the only one! sounds to me its more and more likely to do with the vw made headunit (could be the firmware). I just tried a mate's phone with the AA app but it also went in a connection loop before finally establishing a handshake with the phone. hopefully next firmware update to the car's headunit may be able to fix but but i won't bet on that happening anytime soon.
guess everyone has to trial and error and find ways to establish a successful consistent connection. for me is to forget the car and establish a new connection to the car.
still frustrating as ever and i don't want to have to spend 2 - 3 mins each time before i drive to wait for AA to load.
anyone else having connection issues with other car makes?
rafalucas said:
anyone else having connection issues with other car makes?
Click to expand...
Click to collapse
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
nimdy said:
'Charge only' might be useful, unless AA needs MTP or network connection to operate?
Click to expand...
Click to collapse
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
mikereidis said:
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
Click to expand...
Click to collapse
i've tried various cables but i find the original samsung cable that came with the phone the most "consistent" in establishing a successful connection.
mikereidis said:
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
Click to expand...
Click to collapse
i'll give this a go tonight
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
jonboyuk said:
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
Click to expand...
Click to collapse
Galaxy s6 Stock firmware and my octavia android auto 1.4 work very well.
No luck with LG G3
Good day everyone, I just purchased a 2016 VW GTI and I have an LG G3 with Lollipop 5.01 rooted. and I can not get it to work with mirrorlink or android auto. Mirror link default or AA default. I tried different cables, plugged in car on before the car was on. MTP, PPP, charge. The head unit does see it as an LG phone but nothing works.. usb debugging on or off.. Kind of bums me out. Oh I keep getting a make sure the phone is unlocked message I turned screen lock off, and the phone is awake when I try to connect.
mikereidis said:
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
Click to expand...
Click to collapse
Yes! This is the best option for check if the problem is the HU/car or the phone.
From my point of view typically the most issues are related to the phone (ROM, AA app, etc.). For example, with my previous Lollipop 5.0 one month ago... the AA was inestable. With a new 5.1 phone and with the last AA app version (upgraded 1 week ago) I don't have any problem.
Please, try this before post about problems. Sometimes the problems isn't the car or the Head Unit. :angel:
Hi all. Further to my last post, I'm also sure it is a device/ROM issue. It doesn't work all the time, but most of the time the workaround for me is to open the open apps list, swipe them all off to close them, including AA app, then re-open AA. This increases the chances of my phone connecting to the car, but every so often I get a connection error and have to try again a second/third time.
I think I may have asked before, but is there anywhere we can report these bugs to? AA is technically beta (as with most Google products) so I'm sure they would welcome our bug reports.
Connection Memory ?
Hi,
I have the same experience as many others that the connection to AA is very random. I've tried:
Different phones (Nexus 5 and Nexus 6 on stock Android 6.0)
Different USB cables
AA app on and off
Screen locked and unlocked
All without being able to see a pattern. Sometimes it connects automatically in 15 seconds, sometimes automatically in 1 minute and sometimes I need to manually push the connect on the HUD (VW Passat 2106).
The only thing that is consistent is that once you are connected to AA and then disconnect, if you re-connect the phone it works flawless every time ! It seems to be working even if the re-connect happens after a few minute (e.g. not rigth away). So it seems that either the HUD or the phone has some sort of connection memory. Once it expires the connection problem reappears.
Anyone else that can confirm this ? Any ideas on where the problem can be ? I guess this rules out the USB cabel as suggested by many.
// J
After Google announced almost a full year ago that Android Auto would support phone connections without needing to rely on a USB cable, I have yet to find any news on this.
Is this still happening in the aftermarket HU's? Hoping this doesn't turn into another Android Wear situation where it lacks the attention it needs to make it a market hit.
Hi,
This is called "WIFI Projection", and it's included (hidden) in the last release. No one knows how to enable AND use it. Still in alpha!
I hope current HU with wired AA support can be upgraded to wireless with a simple USB dongle (not a Wifi dongle, but with an AA wireless adapter).
Just to make sure I understood correctly: the option is there in the OS, but it doesn't work on any device as of yet? As if the software support is there, but the hardware support is not?
I'm a bit disappointed that Android Auto wasn't discussed at the I/O keynote... I think there's lots of usability updates required to improve it...
Relevant:
https://arstechnica.com/cars/2017/0...finally-ready-to-talk-about-its-car-os/?amp=1
What gets me: is it really necessary to use a a different name for this? Chromecast comes in audio-only and video forms, Pixel comes in "XL" and "C" forms also, can't they just name it something like "Android Auto Standalone" and call it a day? It serves the same end goal of getting Android into your car's radio/head unit.
Still no news of the phone-based Android Auto and wireless that I can find. That said, if everything will be integrated into the radio to begin with, I'd welcome the lack of tethering. Might even get back to developing Android apps for myself now that I have a use for them, but for my car this time! Hopefully the aftermarket guys will be smart enough to bypass Android for the sound processing though. Would hate for a resource-hogging app to kill my radio!
Hello, I have searched the forum for this topic and I have not found anything related. I've been reading you for several weeks and today I decided to register.
A month ago I bought the Sony XAV AX 100 radio and I am delighted with it. But I can't make Android Auto work with bluetooth, without cable. I have a Samsung S8 and, in the Android Auto app I have checked the option to start by bluetooth automatically but it does not start when I connect the phone to the radio. Can anybody help me? I think it is Sony XAV AX 100 problem that should not support android car with bluetooth, only with cable.
Thank you very much and greetings.
darnelldani said:
A month ago I bought the Sony XAV AX 100 radio and I am delighted with it. But I can't make Android Auto work with bluetooth, without cable. I have a Samsung S8 and, in the Android Auto app I have checked the option to start by bluetooth automatically but it does not start when I connect the phone to the radio. Can anybody help me? I think it is Sony XAV AX 100 problem that should not support android car with bluetooth, only with cable.
Click to expand...
Click to collapse
That headunit doesn't support Android Auto wireless (which uses Wi-Fi). AA will only work if your phone is connected via USB.
You could connect the phone via Bluetooth only and play music and/or use handsfree telephone. But not AA.
Android Auto, because it uses the GPS, is a battery suck. I'm not saying that's a problem, it's just a fact. You would want to plug your phone into power while using AA anyway.
I use NetDot Gen10 magnetic USB cables, and it makes it more convenient, especially since I use both AA and CarPlay.
dragon_76 said:
Android Auto, because it uses the GPS, is a battery suck.
Click to expand...
Click to collapse
That's inaccurate. If the headunit has GPS, Google Maps when running via AA will use that instead of the phone's GPS. I've heard that Google requires AA wireless HUs to have a GPS, but can't point to anything authoritative to back that up. All the units I've seen which support AA wireless (JVC/Kenwood and Pioneer) include GPS receivers.
https://www.indiegogo.com/projects/cardroid-car-pc-android-auto-usb-computer-dongle#/
Is this just a basic Android device using some mirroring software? Would it be possible to do this with a phone?
CarDroid is not a mirror dongle. The link shared has a comparison chart. Mirroring dongles don't have their own operating system and you are pretty much stuck with Android Auto.
The CarDroid is an alternative to Android Auto as it has its own operating system and memory. Also, it doesn't require you to pair with your phone to "mirror" content on your screen. Apart from connecting to BT/Wifi, your phone is basically "set free" and not required to operate CarDroid.
Is it real? Safe to buy?
cesar2010 said:
Is it real? Safe to buy?
Click to expand...
Click to collapse
I bought it this weekend. I hope it will be shipped...
Fishcat7 said:
I bought it this weekend. I hope it will be shipped...
Click to expand...
Click to collapse
Here as well.
Let's see what happens with this thing.
take a video about using
at least on my car, I can not be connected to the car with Bluetooth and android auto at the same time. This could be an issue for me.
Witam i jak urządzenie dotarło? Jak działa jakieś filmiki?
There is this Italian video but it is not too much...
Hi guys,
I received this thing and I must say I am disappointed.
Concept is great and to be honest this is clone of Korean Fine Drive AI 2.
But as RayBomb says device hijack your Bluetooth connection with headunit and you cant use phone just for calling over headunit.
The other big issue is non functional GPS (or missing one I'm not sure).
The project owner is trying to override this with some workaround with GPS tether from your phone but in that case you don't need this device at all.
And cherry on the top.
While flashing it with new firmware it just stopped and now I have something nice looking usb stick.
Device is probably in boot loop and nothing cant see it on usb port. I would feel better if this was my first flashing. When I think a little it is my first time to flash something regular. Since today I was only flashing custom roms and rooted devices and something like this never happened.
My advice is to stay away from this.
Better investment is to make your dedicated AA phone or just to buy phone and root it and install screen2auto what actually I did and it is working like a charm. Bugger is that you need to connect your phone every time with cable but even that is better than non functional device like this.
Only my 2 cents.
Interesting, I'm going to keep my eye on this. It seems like it has potential if they can get the bugs worked out.
I'm using Screen2Auto on a 2 phone setup because I don't want to root my main phone, but it has some problems. Hopefully, they'll get this working.
If they can get it working as intended would you be able to do a Google Assistant search for a phone number and have it make a phone call through your phone?
It's a scam ...
https://www.reddit.com/r/AndroidAuto/comments/m1py7p
...
I can confirm that Cardongle is removing critical reviews and negative comments from their Indiegogo comment section so that they can appear more legitimate and awesome.
DevAuto said:
It's a scam ...
https://www.reddit.com/r/AndroidAuto/comments/m1py7p
...
I can confirm that Cardongle is removing critical reviews and negative comments from their Indiegogo comment section so that they can appear more legitimate and awesome.
Click to expand...
Click to collapse
Exactly like you said.
I was the one refunded and removed after few comments they didnt like.
On their forum also lot of my comments are removed and as I sad I was the one who bricked device. My first brick after so many years without any chance to revive it.
Only thing I regret is that I didnt backed all apps from device with app monster because I like the feature you can use your own launcher like you are on your phone. No annoying AA with his launcher and restrictions what app you can use even when you patch it.
If your device is still alive can you investigate how did they do it yo use AA on headunit as a screen.
Sorry for my bad Enlish but I hope you understood what I meant to say.
CarPC AADongle add Android, GPS, 4G Mini PC to Car
Add Mini PC to Car. Download apps like Netflix from Playstore & emulate games. With GPS & 4G Option | Check out 'CarPC AADongle add Android, GPS, 4G Mini PC to Car' on Indiegogo.
www.indiegogo.com
Any news about this scam ?
GPSSlovakia said:
CarPC AADongle add Android, GPS, 4G Mini PC to Car
Add Mini PC to Car. Download apps like Netflix from Playstore & emulate games. With GPS & 4G Option | Check out 'CarPC AADongle add Android, GPS, 4G Mini PC to Car' on Indiegogo.
www.indiegogo.com
Any news about this scam ?
Click to expand...
Click to collapse
That appears to be different from the CarDongle but it looks similar.
Google CarPlay AI box. They use the wired CarPlay interface to project an Android OS on the car's infotainment screen. They are available now and have more features.