Related
[/B]Hi, just received my TD2 last week and is enjoying it. I have one major issue though. In my car I have a Pioneer AVIC X3 system including GPS, AV and BT. Its the one with the motorized monitor.
Unfortunately it seems that HTC has chosen a different type of BT that is NOT compatible with my Pioneer system.
Does anyone know of any fixes ?
Maybe you can draw more attention to your thread by adding an appropriate title. Good luck finding a solution!
I had a very high end pioneer, never again.
With mine, the problem was that the pioneer won't recognise PDAs, but it will recognise Smartphones and mobile phones. (Each bluetooth device broadcasts what type of device it is.)
I actually told pioneer the problem, how to fix it, and their support would only say "your phone is not on the supported device list". After i put the effort in to help them improve their systems dramatically, they couldn't even be bothered to acknowledge it / forward it to the development people.... so I spent £600 on a kenwood, worked like a charm, Kenwood's bluetooth modules are made by parrot. (also the £70 kenwood I also have works great too)
There are some registry edits that work to make your phone identify itself as a smartphone, as long as it has the MS bluetooth stack, not sure the exact details though, I've not needed to do that since I got rid of the pioneer.
Hi Trinode,
Thanks a lot for your comments. If I was to try the registry edit thing... would you know a link somewhere where I can get this information ? Otherwise I'm probably forced to change the Pioneer system also.
Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
new build with android 2.3.7!
http://iloki.nl/2011/09/30/android-237/
Installation is the same procedure as the CM nightlies. Only rom file is different.
Howto install
cool will give it a shot
gekkekoe123 said:
Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
I've decided to build a rom also for vibrant users. Give it a try: http://iloki.nl/2011/08/06/update-06-08-2011/
Beware, I'm uncertain if vibrant uses the same bootloader as the I9000. Changing bootloader isn't required for GPS support and is NOT recommended for vibrant users.
for more background information: http://forum.xda-developers.com/showthread.php?t=1170031
Please try to centralize feedback in the background topic.
Click to expand...
Click to collapse
Thank you! I love my Vibrant but GPS is a deal-breaker for me.
Sent from my HTC Glacier using XDA Premium App
This does not improve the internal GPS radio in any way. This just gives us a switch to enable a external Bluetooth GPS receiver natively without buggy 3rd party apps. This causes apps such as Google maps or navigation to be much more accurate due to the dedicated GPS receiver hardware. Using my GlobatSat BT-359 I have managed a app reported 0 accuracy and almost always below a 5 foot area. This pretty much makes the internal GPS cry like a newborn baby...
SkOrPn
Sent from my SGH-T959 using XDA App
so you'll need something extra for this to work?
On the download page, you will find step by step instructions on how to use it.
Basically, flash the rom, pair your gps mouse and just enable/disable GPS (using power widget for example).
But read the instructions at: http://iloki.nl/2011/08/06/update-06-08-2011/
it has screenshots and stuff
My rom basically gives you a switch to use our BT gps mouse as if it were your internal GPS. So you will get maximum compatibility , less battery drain and so on. Normally external receivers are way better than the ones that comes with your phone. My gps mouse is giving me 0.8m-2.0m accuracy for example. I was happy if I had 10m on my internal one. Most of the time I could get a lock (already tried soldering and so on).
To use my stuff the requirements are:
Galaxy S I9000/Vibrant -> binary builds. Other devices can be built from source.
NMEA 0813 capable GPS Mouse with Bluetooth Serial Port Profile (SPP)
gekkekoe123 said:
NMEA 0813 capable GPS Mouse with Bluetooth Serial Port Profile (SPP)
Click to expand...
Click to collapse
Does it matter what chipset is being used in the mouse? By the way, I call it a GPS Receiver, "mouse" sounds strange to me, lol....
My unit has the SiRF StarIII chip and is also NMEA 0183.
GPS Protocol Default: NMEA 0183 (Secondary: SiRF binary)
GPS Output Data: SiRF binary >> position, velocity, altitude, status and control
NMEA 0183 MEA0183 V2.2 protocol, and supports commands GGA, GSA, GSV, RMC, VTG, GLL v2.2 (VTG and GLL are optional)
GPS transfer rate: Software command setting (Default : 38400,n,8,1 for NMEA )
Connection: Communication with host platform via Bluetooth Serial Port Profile
Using the 3rd party app "Bluetooth GPS Provider" from the market, it lets me actually select my chip type, in this case SiRF. Does this even matter in this case?
Nope doesn't really matter as long as they output nmea sentences (I haven't seen one that didn't. But it doesn't hurt to check before buying).
I myself am using a MTK2 chipset.
btw: google GPS Mouse ;-)
gekkekoe123 said:
Nope doesn't really matter as long as they output nmea sentences (I haven't seen one that didn't. But it doesn't hurt to check before buying).
I myself am using a MTK2 chipset.
btw: google GPS Mouse ;-)
Click to expand...
Click to collapse
Yeah I already knew its called a mouse, I was just commenting that I do not like it. Its a GPS satelite receiver, or even a Wireless BT GPS puck would have been more appropriate I think... Come to think about it, mine is slightly smaller than a ice hockey puck but rectangled and very heavy for its size. I could easily play ice hockey with it, LOL....
Ok, so good NMEA support is all we need to worry about then. Most excellent...
EDIT: I hear MTK is better than SiRF, but not sure myself...
Synced with the low power mode patches.
new vibrant rom available.
This post is just asking for more clarity.. ..
gekkekoe123 said:
Guys,
I've implemented the external BT GPS for the CM7. Until now I only supplied a I9000 rom and source code. Since vibrant users with CM7 suffers from GPS performance (lack of it ;-) )
I've decided to build a rom also for vibrant users. Give it a try: http://iloki.nl/2011/08/06/update-06-08-2011/
Beware, I'm uncertain if vibrant uses the same bootloader as the I9000. Changing bootloader isn't required for GPS support and is NOT recommended for vibrant users.
for more background information: http://forum.xda-developers.com/showthread.php?t=1170031
Please try to centralize feedback in the background topic.
Click to expand...
Click to collapse
Thanks for your developments and this post, seems to have a great feature for the Vibrant users like my self, if I could understand your post....
External BT GPS...... If I had an external GPS, why would I use my phone....
External BT mouse . . . . this is not clear to me....
This post is just asking for more clarity.. ..
serendipityguy said:
Thanks for your developments and this post, seems to have a great feature for the Vibrant users like my self, if I could understand your post....
External BT GPS...... If I had an external GPS, why would I use my phone....
External BT mouse . . . . this is not clear to me....
This post is just asking for more clarity.. ..
Click to expand...
Click to collapse
He has enabled this phone to take advantage of the common GPS Pucks you see around the world. They do not have a screen of their own, all they do is have the high quality GPS chip like MTK or SiRF StarIII or something similar, and they have their own antenna and they connect via Bluetooth to computers, laptops and smartphones. Smartphones are given very cheaply made low quality GPS systems, but some people like myself included would prefer a much higher quality GPS result on their phone.
Advantages:
1. MUCH higher quality GPS accuracy down to 1 foot or less.
2. Uses less power since Bluetooth is MUCH more power efficient. I had my GPS on over 8 hours yesterday and when I went to bed I was still at 54% battery left, using the built in GPS system my phone would have died long long before then.
3. Lets people use their current GPS puck/mouse. Now I can use my GlobalSat BT-359 GPS mouse. My Samsungs built in GPS system is non-existant and has never worked properly. Now I finally have real GPS, so props to the OP.
This OP in my opinion was very very clear in the first place... You shouldnt roll your eyes or wink like you know what your talking about unless you truly know what your talking about. All you did was show how much you are lacking up stairs. Figured I get to now roll my eyes at your stupid post.
A GPS Mouse is a GPS unit made for smartphones and laptops and they DO NOT have a screen of their own, there are hundreds of them made and have been for many many years. This is what he is doing, letting us use these awesome Bluetooth GPS devices so we can have much more accuracy and bettery battery savings. I see no harm in this.
@the OP, thanks for your great efforts as this was long over due...
new vibrant build available http://iloki.nl/2011/08/24/update-24082011/
gekkekoe123 said:
new vibrant build available http://iloki.nl/2011/08/24/update-24082011/
Click to expand...
Click to collapse
The new Vibrant build still has flashing according to Skitz.... he broke it Im sure, lol....
Thanks SkOrPn for the explanation, this helped greatly.
SkOrPn said:
Click to expand...
Click to collapse
Thanks SkOrPn for the explanation, this helped greatly.
serendipityguy said:
Thanks SkOrPn for the explanation, this helped greatly.
Click to expand...
Click to collapse
Why certainly your most welcome....
I'm using this via Trigger - works BEAUTIFULLY on my BT 359 receiver. Although it was pretty confusing at first - after pairing initially it just said "paired but not connected" - needed to switch to the external first, then reboot, then turn on both BT and GPS (sometimes they turn on together in tandem, sometimes they don't..) before the light on the receiver indicated it was connected to the phone. And even then, it's still reported as not paired.
But that aside, this is ROCKING. I would tell you how accurate of locks I'm getting but GPS Test is freaking out (which seems to have been fixed and needs to be implemented in Trigger)
What are the odds of getting this into CM7 mainline?
strictlyrude27 said:
And even then, it's still reported as not paired.
What are the odds of getting this into CM7 mainline?
Click to expand...
Click to collapse
It reports itself as "Paired but not connected", not as not paired. I mentioned this somewhere else I think in the Trigger thread but now I cant find it. I believe it cant report itself as connected because it does not use a constant on connection similar to that of a BT Headset would. I believe the puck sends data at on/off intervals to short for the phone to display a connection. Just my theory though... My BT Headset on the other hand causes the phone to report as connected, but I think that's because its a constant connection, as obviously an on/off connection would be detrimental to transmitting voice... lol
I can't wait to get this in cm7 source myself, but I wont hold my breath. I wonder if there is anyone we can email to get this pushed along quicker?
Don't worry about paired but not connected message. The most important thing is that is it paired.
Connected is represented by the GPS icon.
flashing -> connected and waiting for fix, or temp lost a fix
solid -> connected and fix
none -> no connection.
Just pay attention to you gps icon and you should be fine. The connection should be there all the time, a fix can be lost temporary if you're going through a long tunnel.
It's generally best to first turn on gps and then enable it on your phone (handshake attempts are initiated from the phone). The first handshake attempt might failed otherwise and you have to wait a little bit for the retry. But eventually it will connect.
New vibrant rom is being build, should be up shortly.
This removes the reboot requirement when switching gps sources. Yes it means no more rebooting
http://iloki.nl/2011/09/08/reboot-requirement-removed/
Hi Guys
Would really appreciate some help with this one, i am sure it been covered to some degree in other threads.
Since owning my unit I have wanted one application to run and I am not fussed about anything else, the app is ALPconnect.
ALPconnect is a application that connects to my radar detector via BT 4.0 only so it displays all the information on the dash for radar frequencies.
https://play.google.com/store/apps/details?id=com.alpriority.alpconnect&hl=en
Due to the limitations in the Bluetooth, no current rom has been able to allow the application to turn the BT on and search for the ALPconnnect Module
http://www.alpriority.com/product/alpconnect-bluetooth-module-gen2/
Over on the other forum i am apart of http://radarandlaserforum.com, one member has spent upwards of 2000$ buying android head-units to see if this app would run and connect on it.
our small thread is ongoing at @ http://radarandlaserforum.com/showt...-InCar-Enetertainment-unit-ALPconnect-Testing about this issue.
I don't normally ask for help, but I could really use some help and I am sure others on the forum that purchased it for that reason would greatly appreciate it too.
This is the last information I received from agentdr8, thank you aswell
agentdr8 said:
It's severely limited, when compared to any other Android device with BT. This is due to the OEM's choice of the BC5/BC6 module, and their poor BT implementation. Instead of routing BT audio traffic through the Android system, like a normal device would, they route it through the MCU. That would be fine on its own, except they route pretty much all BT interactions through the MCU, via serial AT commands, which is very non-standard. Simple things like pairing, or using SPP profile just don't work, or require a bit of finagling.
On top of that, there's code (at least in MTCB; dunno about newer MTCD) in MTCManager that filters which devices can pair via BT for OBD use. It checks the device name and if it starts with OBD, it will allow it to pass to the next step during pairing. I can only imagine they chose to do that so they could sell their companion BT OBD adapters with the headunits?
My XMTC module had accounted for this limitation in name-based filtering (apparently not the only limitation though; if your adapter was at least v1.4 it should work), but it hasn't been updated to work on any 2016 roms. Since I no longer have time to maintain that project, it's been open sourced on my github. The BT pieces could be extracted into their own module, but I thought I had read someone else (maybe MVG70?) had made a BT xposed module for these devices to try and address compatibility issues.
Click to expand...
Click to collapse
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Sent from my iPhone using Tapatalk
shanetrainST said:
Just as a thought
Would the MTCB be able to support external USB BT 4.0 thus removing the need for the messy internal BT
Click to expand...
Click to collapse
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
agentdr8 said:
I think it's been discussed before, and no one has successfully added an external BT adapter to these headunits.
Has that group tried the app on the Parrot Asteroid? I know it wasn't the highest rated Android headunit, but it might be more "standard" than how these ones are configured.
Click to expand...
Click to collapse
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
shanetrainST said:
Thanks agentdr8, but it does not really help the ones that splashed out and bought the HuFei units
Is the reasoning behind the external BT not working because nobody is interested in making it work or is it not technically possible?
Click to expand...
Click to collapse
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Guess the manufacturer is reluctant to release the source then.
Sent from my iPhone using Tapatalk
agentdr8 said:
Since the kernel is not open source, there's very little hope of adding the necessary drivers to support external BT adapters. Aside from that, I don't believe the BT stack that is included in these roms is standard.
I won't say it's impossible, as given enough time and money, anything is possible. But I doubt it's something anyone here can address without the sources.
Click to expand...
Click to collapse
Just a couple of questions
1.Do you know if any developer is currently working injecting the drivers into the kernel, as impossible as it sounds.
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
3.Have any of the manufactures hinted at releasing the source and letting other developers fix the issue with custom roms
Just on another note
I have 30 emails from Eonon saying that their tech cannot do this and have assured me that.
We have our own brand and R&D department.
We use our software.
Click to expand...
Click to collapse
Which I don't believe for a second
I'm quite interested in getting this fixed as well - I have both an ODB2 adapter and Navdy that I'm unable to connect due to this limitation. And the fact that there's no available workaround via External BT is infuriating.
shanetrainST said:
Just a couple of questions
2.If the manufactures were to fix this issue, what things should they include to make external BT work?
Click to expand...
Click to collapse
From my understanding, the only way to get this to work is through an external (USB) BT adapter, since the built-in BT stack sends everything through the MCU instead of directly to android. So enabling the proper USB drivers for BT in the Kernel would fix it. I'm not aware of any other USB devices that don't work (maybe gamepads or other HID devices, unconfirmed) so it seems they've cherry picked which USB devices to allow. Considering the otherwise hackable nature of these devices, it'd make sense to me to just enable all available USB devices and let us plug in whatever we want to plug in.
I'm in the same boat. I have an OBD adapter (Hondash) which refuses to pair. I've tried 2 Xposed modules which are supposed to sort this. I'm wondering if my particular issue is down to my 5.1.1 ROM so might try it on my old RK3066 4.4.4 HU which I gave to my Dad.
So I'm monitoring this thread in the hope a fix is found.
I am doubtful, I have contacted Klyde/Eonon/others and nobody is willing to release the kernel source code or address the issue.
So when someone gets a copy from Klyde/some reseller/MTC or whoever and a developer has the motivation to correct it, that can be the only solution.
I have given up hope on this one
Sent from my iPhone using Tapatalk
Does anyone know the location in the Android file system where the Bluetooth pairings are saved?
FINALLY! Someone with a similar issue. I've got a Valentine One, and the BT module for android, (connecting using YaV1) and I've been trying to get my android unit to pair with it as well. In for potential solutions.
This question may be off topic, and I apologize for that, but are you referring to the app not being able to turn on BT and look for the adapter; just getting stuck at "Turning on bluetooth..."?
I have an OBDII scanner which I can pair no problem. When I use a specific app (OBD Card Doctor Pro (or reg)) and attempt to connect it, I get a prompt letting me know that an app wants to turn on BT. I click allow and then it just sits there and never does anything. Is that the problem ALPconnect has?
Torque does not prompt me with this and initiates the BT connection just fine.
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
monza20vt said:
The main issue here is that the bluetooth hardware is in effect emulated to the android subsystem for the nice bluetooth dialler front end so android has no real control over the bluetooth hardwrae. These headunits have some real downfalls and this is one of them What we need is to break this open and rewrite it. Without sources we can't do that. We could maybe dissasemble bits and replace them in code but the rom is factory odd and hacked to bits!
Click to expand...
Click to collapse
So this emulated effect is what causes my system get stuck "Turnning on bluetooth..." if I understand you correctly? There's no Android control over the BT hardware so the request is just lot in limbo?
Hi all,
First: I used the search function, but I couldn't find a solution. So if there is one, just post the link to the topic.
And now my problem/idea: I have car that comes with a radio which supports Android Auto and Apple Carplay. Unfrotunately, it doesn't support DAB+. I was looking now for a solution to add DAB+ without any additional (visible) screen or remote control. There are some but they mostly are not really working properly.
So I had the idea to add DAB+ by Android Auto. Is there some hardware to do that (if possible without pressing 10 buttons every time I turn on the car/radio)?
Theoretical it should be:
- a USB-dongle (also powered by this)
- on which a Android system is running
- which starts DAB automaticaly
- has the hardware to receive DAB+ signals
- just have to be plugged into the USB-Port of the car
Is there something like that? If not, is it possible of did I forget something which prohibits this idea? How could this be built and what would be needed?
Thanks for your ideas/links/whatever...
PlatinCH
PlatinCH said:
Hi all,
First: I used the search function, but I couldn't find a solution. So if there is one, just post the link to the topic.
And now my problem/idea: I have car that comes with a radio which supports Android Auto and Apple Carplay. Unfrotunately, it doesn't support DAB+. I was looking now for a solution to add DAB+ without any additional (visible) screen or remote control. There are some but they mostly are not really working properly.
So I had the idea to add DAB+ by Android Auto. Is there some hardware to do that (if possible without pressing 10 buttons every time I turn on the car/radio)?
Theoretical it should be:
- a USB-dongle (also powered by this)
- on which a Android system is running
- which starts DAB automaticaly
- has the hardware to receive DAB+ signals
- just have to be plugged into the USB-Port of the car
Is there something like that? If not, is it possible of did I forget something which prohibits this idea? How could this be built and what would be needed?
Thanks for your ideas/links/whatever...
PlatinCH
Click to expand...
Click to collapse
A late but working solution...
USB-Stick (working fine with Android)
Thread for working software for this device. --> latest greatest one
Hi Rigattoni,
Thank you for your reply.
If I understand it correct, the stick is only the DAB-receiver and not the "head unit" on which the android system is running? Or can I make Android running directly on this stick?
Hey Guys,
i searched the Web for a possibility to get AA running on my X70 Pro+ with Origin OS Ocean....
Unfortunately there are only Posts and Threads about the X60 and other Vivo Phones and so on .
The issue seems to be the same.
Has anyone found a workaround to get AA running on Origin OS....?
I was hoping for Android 12 to get the Phone going, but no Idea what time we will get Android 12 and if Vivo sets permissions for AA then.
Cheers and greetings from Germany
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
Thank you very much for the detailed explanation
Im looking for an EZ solution too
But from my knowledge the only work around right now is root the phone and make AA an system app
which is not EZ for vivo since it does not allow to unlock bootloader
There is simply no chance to run AA with x70 pro+ now. The only viable solution are android dongles running on past Android versions and triggering car AA. Or even better - if you have or can buy cheap an Android 8, 9 or 10 phone with full gps and at least 4g ram (could be with broken screen or scratches), you can use it as an interface.
The only way to have android auto to work on your vehicle is to have the one with Funtouch OS (which I have), other than that, you will waste your time in trying to find a way to make it work..
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
Will a dongle fix the connection issue?
piskr said:
Hi,
Right now, there is unfortunately no way to get Android Auto working. After Android 10 Android Auto only trigger car installation of it is a system application. Since there is not the case with Vivo and you couldn't mount AA as a system, you are out of options to make it work.
There is a slight, but really a slight option that it might work with the new Coolwalk version which will be available later this year.
Otherwise, the head unit direct version is also in preparation.
If you want the working AA now, the only realistic option is to buy an Android CarPlay dongle, or using a spare phone with older Android version as a buffer triggered from your phone hotspot (or with a separate sim card).
Click to expand...
Click to collapse
My head unit is after market and supports wireless. I know that my x fold won't hook up. Are you saying if I get carplay dongle I can hook my vivo wifi to it and it will work?
Sonicsoul25 said:
My head unit is after market and supports wireless. I know that my x fold won't hook up. Are you saying if I get carplay dongle I can hook my vivo wifi to it and it will work?
Click to expand...
Click to collapse
The head unit has to support Android Auto. Then you can choose from a variety of dongles. Even though they have more or less the same chip, they are different. Each producer tries to squeeze the most from the device, and they have a different approach.
Basically, you must avoid those, which don't clearly stated that some version of Android is installed. Without Android you gain nothing, it's only wireless connection - for IOS.
Most of them have Android 9 or 10, though in the last time 11 appears as well. That is really interesting, because with Android 11 you must have AA as a system app in order to trigger it on a head unit. It looks like producers now solve that issue.
And surprisingly, the core you get on the head unit, if everything goes ok, is not Android, it's IOS. In that core you have android apps including Google Play.
Since, as I said, every unit has a unique configuration, it's not possible to recommend any. The device that I bought is not in the market anymore, for example.
The very piece that you buy must play well with your car head unit and everything what is behind. And behind is a lot, managing systems for settings, audio and other customization.
You must be aware, when you connect AA dongle, it cuts every other setting related to its management out.
Therefore, the biggest issue might be that you'll lose calling via Bluetooth functionality. Because callings (and old style sms) goes different way than other features. My dongle does support calling but in limited way, without Assistant support and with custom made phone app, where the contact selection is rather difficult. And the next flaw is that it doesn't get along with my car audio system, therefore woofers are not engaged. The dongle doesn't have an equalizer, and I can't remedy it.
There is noticeable lag when starting apps and with commands, but otherwise there is no lag when running. Music, video and Gmaps function without glitches. Yes, you have YouTube, Netflix and any other video app you might be subscribed to. And video runs well with a decent resolution. You can load apps from store or as a sideload. And you can play local files, stored either in the dongle memory or on USB.
That's my experience, others may have different. You don't have necessary to buy a dongle, you can use an old phone with Android from 8 to 10 as a driver. Because, as you may already guess, your actual phone serves only as a hot spot (wireless and if you're lucky bluetooth too - tethering) to provide a signal for AA dongle.
If you want to buy a dedicated device, select one which has reviews from the users with as much as possible similar circumstances and priorities as you have.
piskr said:
The head unit has to support Android Auto. Then you can choose from a variety of dongles. Even though they have more or less the same chip, they are different. Each producer tries to squeeze the most from the device, and they have a different approach.
Basically, you must avoid those, which don't clearly stated that some version of Android is installed. Without Android you gain nothing, it's only wireless connection - for IOS.
Most of them have Android 9 or 10, though in the last time 11 appears as well. That is really interesting, because with Android 11 you must have AA as a system app in order to trigger it on a head unit. It looks like producers now solve that issue.
And surprisingly, the core you get on the head unit, if everything goes ok, is not Android, it's IOS. In that core you have android apps including Google Play.
Since, as I said, every unit has a unique configuration, it's not possible to recommend any. The device that I bought is not in the market anymore, for example.
The very piece that you buy must play well with your car head unit and everything what is behind. And behind is a lot, managing systems for settings, audio and other customization.
You must be aware, when you connect AA dongle, it cuts every other setting related to its management out.
Therefore, the biggest issue might be that you'll lose calling via Bluetooth functionality. Because callings (and old style sms) goes different way than other features. My dongle does support calling but in limited way, without Assistant support and with custom made phone app, where the contact selection is rather difficult. And the next flaw is that it doesn't get along with my car audio system, therefore woofers are not engaged. The dongle doesn't have an equalizer, and I can't remedy it.
There is noticeable lag when starting apps and with commands, but otherwise there is no lag when running. Music, video and Gmaps function without glitches. Yes, you have YouTube, Netflix and any other video app you might be subscribed to. And video runs well with a decent resolution. You can load apps from store or as a sideload. And you can play local files, stored either in the dongle memory or on USB.
That's my experience, others may have different. You don't have necessary to buy a dongle, you can use an old phone with Android from 8 to 10 as a driver. Because, as you may already guess, your actual phone serves only as a hot spot (wireless and if you're lucky bluetooth too - tethering) to provide a signal for AA dongle.
If you want to buy a dedicated device, select one which has reviews from the users with as much as possible similar circumstances and priorities as you have.
Click to expand...
Click to collapse
Thank you for the wealth of information. I Think I will just use my spare phone to run it. Until another solution arises.