Related
I'm trying to use the app (winamp remote) to listen my music library on my Nexus. Went to the market and downloaded and installed on the phone. did go also to get the server application and installed on my pc. opened port 1950 on my rooter. I'm able to establish a connection from my phone to the pc over the net. I see (over remote access on another pc) the player on the pc starting. when i press play in my Phone - so there is a connection established. The only thing i'm not able to see working is the sound on my phone. Can anyone point me in the righ direction? or give a good alternative to use with my pc software. Thanks in advance
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
gmote does this fine for me.
thank you for the answer but i've just installed musikcube after a extensive search. but if i change my mind or if it stop doing the job i'll try the one suggested
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
+1 for gmote
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
mikereidis said:
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
Click to expand...
Click to collapse
Hi,
I have a Wiko Fever with stock Lollippop 5.1.
Please, try these tests:
1) Open AA, push HOME button (the App continues in background), and lock the phone. Then connect to the card and start it. Result: The AA opens in the car automatically.
2) Open AA, push HOME button (the App continues in background), select "running Apps", CLOSE AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
3) Reboot the phone. Don't open AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
It's the same in your case?
manos78 said:
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
Click to expand...
Click to collapse
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
I've been having to open the app before plugging my phone into my Hyundai Sonata. Unfortunately, it sometimes still doesn't launch in the car, so I have to unplug, force close android auto and then reopen. It's a pain to get it started up. I have a Note 4.
Sent from my Nexus 7 using Tapatalk
ireknole said:
I've been having to open the app before plugging my phone into my Hyundai Sonata.
Click to expand...
Click to collapse
That is! You need to open the AA app before plug the phone in the car.
war1 said:
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
Click to expand...
Click to collapse
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
manos78 said:
That is! You need to open the AA app before plug the phone in the car.
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
Click to expand...
Click to collapse
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
My test is:
1) Phone reboot
2) Unlock phone and connect to the car
3) Start the car
4) Try to select AA in the screen of the car
In this order, don't work with my car (VW MY16). I'll try your suggestion. :fingers-crossed:
Thank you!
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
ireknole said:
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not every time of course, I did a reboot just to test,:laugh:
ireknole said:
I think the key is waiting until Bluetooth is connected before starting android auto.
Click to expand...
Click to collapse
Starting AA companion app or AA in the car? Of course, if I start the AA companion in the phone, then the car connects (in my case is indifferent if the car is on after/before or if AA is started after/before Bluetooth).
My concern is: plug the phone and start automatically the AA companion app, even if you don't start it after you reboot your phone. This is the request!
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
manos78 said:
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
Click to expand...
Click to collapse
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
war1 said:
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
Click to expand...
Click to collapse
Not completely really,
After several tests with different order and reboots, I like to confirm that the AA companion app don't need to be started before connect the phone to the car. The KEY point is the BLUETOOTH (yeah!)! If the phone isn't paired with Bluetooth, or the Bluetooth is disabled in the phone, or (and this can be the annoying trouble for some like me) if the bluetooth connection is stalled in the phone... then the AA connection don't work.
So, my recomendation: You can connect the phone to the car in any order, but check Bluetooth if you have troubles.
:good:
I'm finding that even after Bluetooth is connected, it still doesn't start up. Today I tried unplugging and replugging the USB for about 10 minutes before it finally, for no apparent reason, decided to take and launch AA.
Sent from my SM-N910V using Tapatalk
I just read something on Twitter yesterday from Android support and it seemed to help. Go into the Android Auto app in the application manager and clear the cache. Once I did that, the app seems to connect better.
I also found that if I start the app and it doesn't connect, if I go into my active apps and clear out Android Auto, it will connect the next time I plug in the USB.
Sent from my SM-N910V using Tapatalk
I think all the car radios work differently. I don't turn on any Bluetooth, or run the AA before plugging. All I do is plug in, and the Bluetooth and everything else connects automatically. So I guess it all has to do with your initial setup.
I've tried three Roms (2 Oreo and 1 nougat) and I can't get Android Auto to work with any of them. Has anyone gotten Android Auto to work with any of the Roms available here?
Sent from my Nexus 6 using Tapatalk
It has worked well for me on the latest 7.1.2 Pure Nexus ROM. I am currently running AICP Oreo and it works great. It also worked on S.I.X. ROM Oreo and Republic of Madness Oreo ROMs for me.
What issues are you having?
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
imaGine00 said:
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
Click to expand...
Click to collapse
Have you tried a different cable? I had to try 3 of them before it worked right to start with in my F150
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
imaGine00 said:
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
Click to expand...
Click to collapse
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
AAuto works great on my N6 with LineageOS on my Kia Sportage. It's a brand new 2018 Kia purchased two days ago. One of the main reasons for that purchase was AAuto in the electronics package.
bfmetcalf said:
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
Click to expand...
Click to collapse
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
imaGine00 said:
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
Click to expand...
Click to collapse
Try clearing data for AA and see if that helps.
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Negotiator50 said:
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
This did the trick!! Thank you so much!
Sent from my Nexus 6 using Tapatalk
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
woooooh that did the trick ! Thank you !!
I use it with crDroid 4.0 Beta 6 and everything work ...
Hi there!
Does anyone succeed in having two phones working with AA ? One stays connected permanently to AA, the second one is connected to BT for calls and texting.
My experience is that even if both are correctly connected when they are alone, once together all is a mess. As soon as the second phone gets connected to AA, the first one gets deconnected from BT.
I tried to break BT connection within the second phone. It gets connected anyway to AA, but this didn't solve the issue. The first one was ejected from BT,stating that another device was already BT connected (even if BT is broken).
Any help ? BT Mac address modification on the first phone to match second phone ?
Thanks in advance !
i been toying with the idea to do this.
sorry i just need to ask, even you disable auto connect Bluetooth in AA setting?
Sent from my HUAWEI MT7-TL10 using Tapatalk
ahhl said:
i been toying with the idea to do this.
sorry i just need to ask, even you disable auto connect Bluetooth in AA setting?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Haven't tried yet but surely a good idea ... On my way to test !
When you say that you've been toying, do you mean you get it to work or not ?
My purpose is to use a Nexus 7 2013 (not LTE version) as a permanent device connected to AA, and use my phone connected to BT, thus to avoid plugging/unplugging ...
No joy ... Using BT or not has no effect ... Phone is deconnected when tablet is connected to AA...
DR400 said:
Haven't tried yet but surely a good idea ... On my way to test !
When you say that you've been toying, do you mean you get it to work or not ?
My purpose is to use a Nexus 7 2013 (not LTE version) as a permanent device connected to AA, and use my phone connected to BT, thus to avoid plugging/unplugging ...
Click to expand...
Click to collapse
i tried...
it seems the Bluetooth still auto connect.
theres go my plan
any other way to delete pairing. maybe it work. just my guess
Sent from my HUAWEI MT7-TL10 using Tapatalk
ahhl said:
i tried...
it seems the Bluetooth still auto connect.
theres go my plan
any other way to delete pairing. maybe it work. just my guess
Click to expand...
Click to collapse
Deleting pairing has no impact. I even succeeded in breaking BT to avoid AA to wake it up but no joy either.
Whenever AA gets connected to the phone (via USB), any other BT connection is rejected stating that another device is already connected ...
Spoofing BT Mac address of soon to be BT-connected phone with the one of AA-connected phone might be a solution ? But not enough geek to try this one...
Seems strange nobody came across this idea ... please help if you did !
I worked it out, permanently disabling the Bluetooth using root. I described it in this thread.
https://forum.xda-developers.com/an...droid-auto-maps-spotify-iphone-calls-t3746308
Pixege said:
I worked it out, permanently disabling the Bluetooth using root. I described it in this thread.
https://forum.xda-developers.com/an...droid-auto-maps-spotify-iphone-calls-t3746308
Click to expand...
Click to collapse
Tried that already... Disabling BT doesn't prevent HU from detecting and kind-of BT pairing the device, ejecting in the same time the phone ... At least in my situation...
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
i been toying wirh aa2. 9 or aa3. 0 because of non working issues
i accidently noticed my bt does not connect to my car but aa2. 9 still works.
i need to replicate this again.
if this work, 2 phone can still works
Sent from my HUAWEI MT7-TL10 using Tapatalk
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Please what application to spoof BT MAC Address you did you use? I can find application only for wifi MAC ardress changing.
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Try using "app quarantine". This it the only application that really stoped my BT for good.
So success with 2 phones?
Do you need to be rooted to spoof the BT MAC address?
Thanks
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Thanks for this.
I kind of have it working but cannot control the phone connected by BT from the head unit (which still tries to make calls from the phone connected via AA).
Calls made directly from the phone do however go through the head unit.
Is there a way to control the BT phone via the head unit with the other phone connected via AA?
Android Auto on the navigation screen, iPhone connected via bluetooth for phone calls. VW Passat B8 2016
thank you to Pixege !
the method described it realy works (tested on Galaxy S7 and galaxy S5) in function on galaxy S5
it works ok if tha main phone it is conected in HFP mode
but because I have and rSAP mode and I'd like it want to use this type of conection but here are some problems..
the reason it is because I try to build from a galaxy s5 SM-901F (6.0.1, version MMB29M.G901FFXXU1CQE3 rooted with chainfire ) a standalone device im my car for use android auto in the car independent of my normal phone (galaxy S8)
so I want to use in the same time 2 android phones but both want to conect by bluetooth to the car (VW Discovery Pro)
to do that I disable via Esentiale root bluetooth proceses I found and works fine if the main S8 it is conect by HFP protocol
but if s8 is conected by rSAP (and I want to be conected by rSAP) when the second phone is conected by usb(with blutooth off) somehow disconect the sim from main S8 phone (but on the phone show like the rsim it is still working) but not conect to the second phone
if I first conect the android auto (S5) and after connect the phone (S8) rhe rSAP conection works fine
if I first conect the phone (S8) and after connect the android auto (S5) the rSAP conection not work on S8
anyway I want to disable the rsap on the galaxy s5 , how can I do this?
i solved in this way
https://forum.xda-developers.com/an...general/car-dialer-instead-aa-dialer-t3809621
deleted. wrong response..
I have an Active 2, Wifi version SM-R820 paired with a Huawei P40 pro. Remote connection in Galaxy Wearable is on and the samsung account is logged in.
But if connected to wifi only, as standalone, there are no notifications.
With BT everything is working almost fine, because sometimes I found the watch disconnected from BT, I have to open the Galaxy Wearable app and after it connects automatically.
Any ideas?
Problem solved.
I have to unckeck "manage automatically" from Settings - Battery - App launch the apps:
Galaxy wearable, Samsung accessory service, Galaxy active 2 plugin, Samsung Health.
I have a Galaxy watch 3 SM-R840 and when I connect it to wifi I can't download or update anything, I reset it to zero and it remains the same, any ideas please
FMR1959 said:
I have a Galaxy watch 3 SM-R840 and when I connect it to wifi I can't download or update anything, I reset it to zero and it remains the same, any ideas please
Click to expand...
Click to collapse
What do you mean by "download or update anything"?
In remote connection mode you can only receive notifications and use the Find watch and phone functions.
upgrade said:
What do you mean by "download or update anything"?
In remote connection mode you can only receive notifications and use the Find watch and phone functions.
Click to expand...
Click to collapse
I mean When I am connected to the phone and I connect to the wifi I cannot download or update anything, it only works with bluetooth, before I could
FMR1959 said:
I mean When I am connected to the phone and I connect to the wifi I cannot download or update anything, it only works with bluetooth, before I could
Click to expand...
Click to collapse
That's the way it's been designed, I think. WiFi on the watch is only meant to connect to your phone "remotely", when Bluetooth connection fails. In the remote connection mode you only can receive notifications and use some basic stuff like Find my watch etc. Open your Galaxy Wearable app on your phone when the watch is connected through WiFi and you'll see most functionality is greyed out.
Solved, I tried it with another wifi network and it works perfect, thanks !!!!!
upgrade said:
I have an Active 2, Wifi version SM-R820 paired with a Huawei P40 pro. Remote connection in Galaxy Wearable is on and the samsung account is logged in.
But if connected to wifi only, as standalone, there are no notifications.
With BT everything is working almost fine, because sometimes I found the watch disconnected from BT, I have to open the Galaxy Wearable app and after it connects automatically.
Any ideas?
Click to expand...
Click to collapse
Hey Mate, can you tell me exactly how did you do this?
I tried tons of things but the remote mode just wont work with my p40 pro, I have google services , maybe that is the issue?
No mater why I do it only wortks with bluettoth, nothing with wifi or LTE, my app just doesnt detect my phone