Related
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
I have the same issue, really annoying so would love to know the answer
Tafkas.Net said:
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
Click to expand...
Click to collapse
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
jac said:
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
Click to expand...
Click to collapse
Mine is set to NOT be visable to others & my bluetooth GPS device just ha a on/off button.
paul8811 said:
Mine is set to NOT be visible to others & my bluetooth GPS device just ha a on/off button.
Click to expand...
Click to collapse
If your concerned about Security you can always change the Pairing codes.
and or turn off bluetooth when not needed.
I'm unaware of any cases where one can connect unless there paired, so in most cases access needs to be allowed on both ends, usually needing pairing codes. Even if it is one way, an approval code will still be needed.
What I found is this, if you want automatic connecting with one way pairing codes i.e. (Car Stereo to PDA or GPS to PDA) You'll need to allow "make device visible" checked off. The usual cause is a memory storing issue with the GPS or Car Stereo. I know that on high end Stereo's and GPS's they have on board memory which will save connection settings, where you'd put pairing codes on both ends and it will save the settings, thus negating the need to leave visible.
Don't know if I answered your question?
Hope I was able to shed some light on the subject....
Good Luck!
hey all
I cant seem to find a lot of info about this topic, so hoping you guys can help me out somehow.
is there any way of getting WM to join to handsfree bluetooth profile when i'm in my car (using pioneer headunit)?
reason being is pioneer head units require you to be connected to the phone in order to use the head unit to make calls, phonebook, etc
with my nokia back in the day, provided bluetooth was on, i would sit in my car and turn my ignition on. about 10-15 seconds later, the headunit joins with the phone. the phone says its connected to 'Pioneer BT unit' and the headunit shows the battery and signal level, and shows the correct phonebook.
with my jasjam (running blacksatin wm6 - although had the same problem on wm5), the pioneer unit doesn't join automatically... it is only after i receive or make a call using the phone, that it quickly joins to the headunit. even then, the person could have started talking before the audio fully comes through...
however this is not a problem there on, as once the bluetooth connection has been made, it remains, and everything works as it should.
so is there any registry hacks or programs i can run that will allow the headunit to make the connection to the handsfree profile once ignition is on in the car?
Cheers,
Bill
hi bcx7,
I had his problem too. It may depend on what head unit you are using, but perhaps the solution is the same.
my pioneer head unit is a DEH-P75BT. It looks for a smartphone, but doesn't recognize the hermes as it's classed as a pda phone.
Solution:
Change the COD (Class of Device) from a PDA device to a smartphone device.
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my T-Mobile Vario II has the value: 1048852 (decimal) for WM5 & 5374228 (decimal) for WM6. Change this to: 5374476 (decimal).
3. Soft restart your device
4. Your device should dentify itself as a smartphone, and my pioneer unit finds it without problems. Note that for my Vario II, I also have to discovery mode always on, so I also protect it with a PIN code.
On the head unit, scan for the devices, save it in one of the P1, P2 positions etc. Then when you switch on your ignition, the head unit should recognize it.
One final tip. My head unit doesn't see the Vario II unless the screen is on (device not in standby). If the screen is off (device in standby), and even though bluetooth is on and in discovery mode, the head unit won't see it. Once connected I put the device in standby and it stays connected just fine.
I found this information a while back on this forum, so credit to the original poster - sorry don't know who it was.
Hope thats helps.
Mike
Hi @ all,
just got my HD2 with german ROM and one of the first things I tried out was to get a connection to my car (Audi A6) through the remote sim access profile (SAP, rSAP) - but it didn't work...
Does someone use the HD2 in his car using the sim access profile, as available in Audi or VW cars?
I have
- Audi A6 Avant (model 03/2008)
- using the "Audi rSAP Adaptor" in the car cradle, located in the arm rest
- everything in the HD2 is activated for Sim Access
Result:
HD2 and car are connecting, I have to put the 16 digit security code in my phone, but after that the SAP mode does not start, and so I have no access to my phonebook. It seems that I only have a "normal" bluetooth handsfree connection, because the HD2 still shows that he is booked into the mobile network - and when rSAP is active, the phone itself disconnects from the network and "falls asleep".
I restarted my HD2 several times, also the rSAP-Adapter by turning ignition of the car off and on until the adaptor switches off, deleting the connections, creating new connections, but nothing helps...
Any comments or experiences from other users are highliy appreciated
Finally, I have to remark that my HTC Snap, which I just upgraded to WM 6.5, works very good im my car with the rSAP - no problems at all, I get all my contacts in the MMI.
Thanks in advance,
Jolig
Just got my HD2 and am having the same problem.
I'm trying to connect with a 2009MY Skoda Superb with the rSAP bluetooth kit.
This works fine with my E71 and my HTC Touch Cruise.
I've been told that there used to be an issue with OBEX authentication on previous versions of Windows Mobile. Apparently, it was important to disable this authentication. However, I can't see the checkbox in the version of WM that the HD2 is running.
Does anyone know what registry entry this checkbox might have been changing?
Thanks,
Bagpuss.
Thanks Bagpuss,
who gave you this information?
I hope someone can solve this problem....but I fear we have to wait until we have more HD2 - owners
-----------------------------------------------------
EDIT:
I just have read something about the "Schaps Advanced Configuration Tool" where someone with similar problems activated OBEX (but it was an older Win Mobile device, and some months ago) - perhaps this could help?
But I just installed version 3.3 of this tool, but it doesn't work on my HD2...
Hi Jolig,
Check out this thread:
http://briskoda.net/superb-ii/howto...us-rns510-using-non-compatible-mobile/131709/
on Briskoda.net.
One of the guys there had lots of problems getting his WM phone to work, and posted the fruits of his labours.
From what I can tell, we can't use the CAB file he mentions, as rSAP is built into the OS version that the HD2 uses.
I've actually logged this issue with HTC, and am awaiting their response. My company is considering the HD2 as our next standard handset, and we won't go for it unless the rSAP functionality works with all VW/Audi group cars.
I'll let you know if they get back to me.
Bagpuss.
Thx Bagpuss,
and yes, in my opinion it's a mess that the rSAP is apparently VERY unimportant for most people or manufacturers...otherwise we wouldn't have this trouble....
I will come back too if I should find some news.
Had the same problem, tried lots of stuff but none of my WM devices is able to work with the rSap protocol. Gave up on it and then my Skoda Columbus system was stolen.
Replaced it with a JVC 7000 with detachable front. Disabled the rSap carkit and am now using the JVC BT carkit wich is working great. The problem is in the MS BT stack. It is not supporting the rSap the way it should. Only phones that work flawlessly are Nokia's I'm afraid...
The lack of rSAP support is what made me ignore the iPhone this time around.
I was hoping that the HD2 would be a viable alternative, but sadly, it doesn't look like this is going to be the case.
As I bought it over the phone, then I've got 7 days in which to return it. If I can't get it to work, then I guess I'll be getting an N97 or N97 Mini (which will definitely work). :-(
Bagpuss.
@ Bagpuss,
otherwise, as I wrote, I can recommend trying the small HTC Snap (or also called Maple?).
Ok, this one has no touch screen and also a very small screen - but I can confirm he works with rSAP and is not too expensive. I will keep this one, although I now have the HD2
As to Bagpuss' information concerning the OBEX, I tried the following:
- installed the newest .NET framework version
(that was necessary to get Advanced Config Tool v 3.3 running)
- install Schap's Advanced Config Tool
- in the menu "Bluetooth", I enabled OBEX
- after that the config tool does a soft reset
...still no success....no SAP and no phone book
I also wrote an email to HTC - it's really annoying, having SAP in the phone etc. and nothing works.
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Hi Binks821,
Binks821 said:
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Click to expand...
Click to collapse
Can you confirm if your Golf has the premium bluetooth preparation?
There are two different versions of factory bluetooth kit for the RNS510, one which simply acts as a handsfree device, and the other (premium) which is a complete GSM phone.
It's the premium kit which uses rSAP, and which seems to be incompatible with the HD2.
You can tell if your Golf is using rSAP by checking to see if the signal strength meter on the HD2 shows any bars when connected to the car. If it does, then it's not using rSAP. If you see the signal meter with a little x in the corner, then it is using rSAP.
If you do have rSAP working, then I'd really like to know which firmware version your RNS510 is running, and also which firmware version you have in your HD2.
Thanks,
Bagpuss.
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Hi Binks281,
Thanks for the confirmation.
I've now done some further testing in my car, and managed to have some success.
This is what I did.
In the car:
1) Remove all device pairings from the bluetooth system in the car.
On the HD2:
1) Perform a hard reset.
2) Turn on bluetooth. Make HD2 permanently discoverable.
3) Make sure rSAP is enabled (it is by default).
4) Turn off SIM pin (turns out this isn't necessary, but I wanted to make things simple).
So, at this point, I have the car system with no paired phones, and the HD2 with factory settings and no personal data (contacts etc.). I also made sure there were no contacts on the SIM card.
Back in the car, I perform a device search, and it detects the HD2.
I select the HD2, and the car displays the pairing password (1111 2222 3333 4444).
On the HD2, I enter the password.
I then get a prompt saying that Skoda_rSAP is trying to connect to the remote sim access service. I say allow, and also tick the box to allow all future connections.
After about 10 seconds, the maxidot in the car says 'New SIM card recognised', and prompts me to create a new user profile. I called it 'HTC_HD2'.
After about another 15-20 seconds, the car should extract the SIM details from the phone and the phone name, network and signal bars should appear in the car display.
You can now make calls, but there is no phonebook.
Given what others have said about the phonebook access, I'm pretty sure that this is what was stopping the pairing from working the first time I tried it. I've heard various stories, some which say that the phonebook access only works with SIM card contacts, some which say it only works with OBEX authentication switched off and so on.
If you look at the paired devices screen in the phone, then you can see connections coming into phone. First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
I'm still trying to work out what is causing the problem with the phone, but I have done the following things:
1) Told the car to only sync phone memory contacts. By default, it's set to sync both SIM and phone memory. You can configure this on the car by going to Settings -> Phonebook -> Select Memory, and choosing 'Mobile Phone'.
2) Created four contacts in phone memory, one with only 1 mobile number, one with 2 numbers (mobile and home) and another two with three numbers (mobile, home and work). I've then gone into Settings -> Phonebook -> Upload and sync these across to the car.
So far, this has worked fine and disconnecting and reconnecting to the car works without a hitch.
I'm now going to try syncing a small subset of my contacts with ActiveSync to see if this also works.
If it does, then I'll gradually increase the number until it either works, or fails.
I'll report my progress here.
Bagpuss.
Thanks Bagpuss,
sounds interesting!
I think tomorrow I will try this also:
- remove all paired phones in the car-system
- delete all contacts
- disable SIM Pin
Temporarily I am not sure if I will do a hart reset in the first step because I've already installed so much... When the work fails, I thing I must do it
I will report what happened.
---------------------------
EDIT:
Ah, come on...TV this evening nothing interesting, wife in bed...I tried it, including hardreset
No success.
Bagpuss, what I detected:
First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
Click to expand...
Click to collapse
This connection to the Sim Access Profile I see also, but only for one second, then it dissappears and then the connection "Handsfree" comes up - and this one remains....
I do not know else what to do.
I now reconnected my beloved HTC Snap/Maple, and now I will start installing my apps on the HD2....
Hi Jolig,
Sorry to hear that it didn't work.
By the sounds of it, the Audi system is somewhat different to the VW/Skoda one. From what I can tell, your system also appears to support using phones in handsfree mode (I'm guessing that the iPhone works in your car).
In the VW/Skoda cars, you can either have a car kit that acts as a handsfree device or one that uses rSAP, but not both.
It could just be that the HD2 isn't responding to the rSAP request quickly enough to satisfy the MMI. In that event, it falls back to using handsfree mode.
When it shows 'handsfree' on the HD2, can you use the MMI to make calls?
This whole area seems to be a bit flaky on the HD2, as I still can't work out why mine didn't work when I first tried.
Bagpuss.
Binks821 said:
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Click to expand...
Click to collapse
Hello Binks821,
I believe that I have the same hardware situation like you but I can't get my HD2 started on my VW Passat with the Premium FSE. The problem is, that I can go through the whole "finding and connecting process" and can save the PIN but then the Connection gets lost between the HD2 and the PFSE. If seems that the PFSE can't connect to the Network (E-Plus) but why the BT-Connect gets lost in this case.
Maybe you can help me to get it work. Thanks a lot!
Negropo
Hello everybody,
maybe I found a solution that work for every sap-handsfree-set. I tried the hint was given on the german car forum "motor-talk" for the connection problem between a vw pfse and the htc touch diamond with wm 6.1 or 6.5.
The trick is that you have to disconnect the HD2 from the pfse by manual when the car first want's to connect automatically. You have to go to the BT-Setup to the tab where are the connected devices listed. If you click on the "+" right of the name of the device you should be seen the tab "Remote Sim Access" or in german "Sim-Zugriff". When the car connect's to the HD2you have to stop this by pressing disconnect in the right below corner of the HD2 screen. Then the connection is terminated. Now you have to start the connection manual over the menu in your car. In a VW you have to press only "connect" in the MFA. And then the HD2 should connect without problems. I don't know why it works but it does. Maybe there is someone here who can explain it and find another "automatic" solution for this problem.
Regards Norman
Well, I don't have a VW but an Audi with an rSAP-Adaptor in the middle arm rest. I fear this also doesn't work for me.
The problem is that this Tab "Sim Access" only appears for just one second, so I have no chance to make anything whithin this single second....and after disppearing of the tab "sim access" another tab "handsfree" appears - and stays. So it seems my Audi only recognizes a handsfree profile. I don't know why,
Temporarily I am happy that I still have my HTC Snap, which is working very fine with rSAP
@ Negropo, can you tell me in which thread at motor-talk you found that?
Thanks,
Jolig
Hi guys,
rSAP works fine with my Audi A4 BTA. I made the HD2 discoverable for any device and I activated the SIM access in the HD2 BT settings. Then I start searching for Bt device on my Audi BT and initiated the connection with the HD2.After inserting the 16 character pin everything works fine.
By the way ... the connections seems to be very stable. With the Touch Diamond I had from time to time connection interrupts where it was necessary to reset/restart the Touch Diamond again.
Best regards,
Matthias
@ Matthias,
"BTA" means that you have the built-in phone with rSAP, right? Is it a brandnew A4?
Hi there,
I have a use case which I haven't found a perfect Android App or solution that can handle it perfectly. I'm currently looking at possibly using Tasker, but since it doesn't offer trial/lite version so I can't tell for sure if it would work or not.
Here is my use case and some of its characteristics (and limitations):
1. Normally when I'm at home, I want my Android phone (Samsung Galaxy Note 3, running Android 5.0 Lollipop) to automatically:
Turn ON Wi-Fi
Turn OFF GPS (location) - to save battery
Turn OFF Bluetooth - to save batter
2. When I'm driving, I hope my Android phone can automatically detect that I'm driving (moving over 10 MPG+), and will automatically:
Turn OFF Wi-Fi (so that it won't keep searching for Wi-Fi signal)
Turn ON GPS (location) so that I can use Google Map or Waze
Turn ON Bluetooth so that it would automatically connect to my car stereo
3. When I'm at work (M-F) or "indoor", I want my phone to automatically:
Turn ON Wi-Fi
Turn OFF GPS (location)
Turn OFF Bluetooth
I have tried several Android apps, but none of them can do this perfectly. "Geo-location" or "time-based" triggers would not work well (based on my current testing). I also tried to use NFC Tools, but unfortunately since I have a thick case for my Note3, so the NFC tags did not work. Any suggestion would be highly appreciated. Thanks!
Hi,
Tasker should do this job pretty well.
Where I would not afraid of battery drain when GPS is on. When no app uses GPS, it is switched off.
My wifi, bt and GPS is switched on all-time and with my new battery I have perfect battery life...
Cheers big
Gesendet von meinem SM-N930F mit Tapatalk
Hi
I have Samsung Galaxy S20 with Android Version 11. Yesterday i installed Android 10 Unit for my BMW F46. Zlink app is version 4.0.7.
its not possible to use zlink android auto wireless, it work only with USB cable connected.
iPhone CarPlay work wireless.
Can someone help me, why its not working wireless for Android Auto?
hello, did you find any solution for that?
Have you opened the android auto settings and enabled the wireless android? That will be found on your phones...
Yes, it finds the bluetooth to connect with but Zlink just stays on Waiting.
Seller told me Zlink is only wired but I cannot believe all over the internet it is shown as wireless and just the version I have is not...
dzippy1215 said:
Yes, it finds the bluetooth to connect with but Zlink just stays on Waiting.
Seller told me Zlink is only wired but I cannot believe all over the internet it is shown as wireless and just the version I have is not...
Click to expand...
Click to collapse
I have same issue, zlink just says waiting.
If I use wired connection, then android auto works...but havent managed to get it working wireless
I already tried enabling developer settings "Add wireless projection settings" and the regular Wireless Android Auto checkbox.
At this point I'm not sure if its something to do with my zlink app, when I go to the about, it does seem to offer option to get more features
Says:
Activation successful
Wired-Carplay + Android Auto
When I click on the more features, says
Wireless-CarPlay
Wired-CarPlay
Android-Auto
[wla,,,id-cp]
And a Wechat link
Eu tenho o android auto versão 10. alguém tem uma solução para instalar o zlink? qual versão você instala. obrigado
bObf2a5a83
isoo1905 said:
Hi
I have Samsung Galaxy S20 with Android Version 11. Yesterday i installed Android 10 Unit for my BMW F46. Zlink app is version 4.0.7.
its not possible to use zlink android auto wireless, it work only with USB cable connected.
iPhone CarPlay work wireless.
Can someone help me, why its not working wireless for Android Auto?
Click to expand...
Click to collapse
I got wireless android auto working with mine. I am using the Wizanic 9" Android tablet for Nissan Altima 08-12. I would notice that when I would launch Zlink, the system tray would show wireless tethering, but there were 0 connections. I had bluetooth connected and I could use the standard bluetooth features (hands free calling, BT music, etc), but wireless Android Auto wouldn't work. These were the steps I took:
1. I had to unpair bluetooth from my phone to the android tablet. I made sure to delete the information from both the phone and the tablet.
2. Because I had previously tethered my phone to the tablet, I also removed the connection from inside Android Auto settings. Not sure if this was necessary, but I wanted to start fresh.
3. Next I started Zlink then reconnected my phone to the tablet via usb cable.
4. After it was connected and verified, I disconnected the usb cable. I went into the Android Auto settings and proceeded to connect via bluetooth. It was important that I connected the BT in this method, because previously when I would enter Android Auto settings I couldn't see the BT connection to the tablet.
5. With BT connection established, next I opened up the Zlink app. It was still stuck on waiting. Also in the system tray I could see the wireless tethering still showed 0 connections. When i clicked on the message for wireless tethering it opened up the settings for wireless hotspot. I created the wireless hotspot (make sure to take note of the name and password.
6. Add the wireless hotspot to your phones wifi manually (this is only necessary once as your phone will remember the network so this step should not need to be repeated every time you start your vehicle). You should be able to connect to the wifi of the tablet. Once your phone is connected it should say it is connected but there is no internet. That is normal.
7. If the Zlink app isn't opened, reopen the zlink app and Android Auto should start automatically. For me, Android Auto started once the wifi connection was made because I still had zlink open.
8. Each time you start your vehicle, Android Auto will not start automatically. You have to repeat steps 5+7 (6 is not necessary). It is important to repeat step 5, just make sure to use the same credentials you used initially. After you repeat step 5 your phone should automatically connect. Although one time I had to enable WPS in the tablet settings to get my phone to connect.
dzippy1215 said:
hello, did you find any solution for that?
Click to expand...
Click to collapse
Try this it worked for me https://forum.xda-developers.com/t/zlink-wireless-android-auto.4375459/post-87599171
Ferns45 said:
I have same issue, zlink just says waiting.
If I use wired connection, then android auto works...but havent managed to get it working wireless
I already tried enabling developer settings "Add wireless projection settings" and the regular Wireless Android Auto checkbox.
At this point I'm not sure if its something to do with my zlink app, when I go to the about, it does seem to offer option to get more features
Says:
Activation successful
Wired-Carplay + Android Auto
When I click on the more features, says
Wireless-CarPlay
Wired-CarPlay
Android-Auto
[wla,,,id-cp]
And a Wechat link
Click to expand...
Click to collapse
I got it working, see if this works for you https://forum.xda-developers.com/t/zlink-wireless-android-auto.4375459/post-87599171
Hope that can help you get wireless AA.
Autokit - Wireless CarPlay Dongle Special for Android Head Unit
Download Autokit Apk file and install it in your android car stereo. Let your car have CarPlay and be wireless.
autokitcarplay.com
Does Zlink have the android auto wireless icon?
If so it's pretty easy to solve actually, but a little annoying haha.
1° Make the following adjustments in Android Auto:
Click a few times on version on the android auto screen until the pop-up asking if you want to enable development options appears, click yes, click on the three dots in the upper right corner, and click with developer settings. Here you can make some adjustments to your liking, but the option we are looking for at this moment is video resolution, set it so that it accepts up to the highest resolution allowed, in my case for example 1920x1080 or 1080x1920, go back to the previous screen and look for the option Start android auto automatically and switch to always option.
2° Making the wireless connection:
Open Zlink, at this moment your device is already connected with the head unit so zlink does not make the necessary switch for it to work wirelessly, disconnect your device from bluetooth and wifi, turn on wifi and bluetooth again, when connecting with the head unit again, the head unit will automatically create a hotspot point and android auto will connect, it takes a few seconds.
Note 1: If in the zlink settings you have the option to adjust resolution for HD screens, disable this, this causes the android auto to not connect wirelessly!
Note 2: for the next times, just open zlink, disconnect bluetooth and connect again wait a few seconds, if it doesn't work, turn off wifi and bluettoth and turn on wifi and bluetooth in this order.
Hope this helps.
Im on a KSW unit with 12.3" screen and SD662. Firmware 2.4.2 Android 11. All works and no issues. AA with ZLink works without issues once I open zlink (I think its zlink 5), AA starts up, BUT HD is not working (HD is on in settings, but screen is not fully filled). It looks like a 4:3 picure with big black bars right and left.
if I turn OFF HD in ZLink, I have fullscreen, but its not HD. When I got my HU first in May 2022 (I think back then it was firmware 1.5.2) HD setting in ZLink changed my AA to HD and fullscreen..
Any idea how I can get HD and fullscreen on my unit?
THANKS!
PCTechGuy said:
I got wireless android auto working with mine. I am using the Wizanic 9" Android tablet for Nissan Altima 08-12. I would notice that when I would launch Zlink, the system tray would show wireless tethering, but there were 0 connections. I had bluetooth connected and I could use the standard bluetooth features (hands free calling, BT music, etc), but wireless Android Auto wouldn't work. These were the steps I took:
1. I had to unpair bluetooth from my phone to the android tablet. I made sure to delete the information from both the phone and the tablet.
2. Because I had previously tethered my phone to the tablet, I also removed the connection from inside Android Auto settings. Not sure if this was necessary, but I wanted to start fresh.
3. Next I started Zlink then reconnected my phone to the tablet via usb cable.
4. After it was connected and verified, I disconnected the usb cable. I went into the Android Auto settings and proceeded to connect via bluetooth. It was important that I connected the BT in this method, because previously when I would enter Android Auto settings I couldn't see the BT connection to the tablet.
5. With BT connection established, next I opened up the Zlink app. It was still stuck on waiting. Also in the system tray I could see the wireless tethering still showed 0 connections. When i clicked on the message for wireless tethering it opened up the settings for wireless hotspot. I created the wireless hotspot (make sure to take note of the name and password.
6. Add the wireless hotspot to your phones wifi manually (this is only necessary once as your phone will remember the network so this step should not need to be repeated every time you start your vehicle). You should be able to connect to the wifi of the tablet. Once your phone is connected it should say it is connected but there is no internet. That is normal.
7. If the Zlink app isn't opened, reopen the zlink app and Android Auto should start automatically. For me, Android Auto started once the wifi connection was made because I still had zlink open.
8. Each time you start your vehicle, Android Auto will not start automatically. You have to repeat steps 5+7 (6 is not necessary). It is important to repeat step 5, just make sure to use the same credentials you used initially. After you repeat step 5 your phone should automatically connect. Although one time I had to enable WPS in the tablet settings to get my phone to connect.
Click to expand...
Click to collapse
I've followed these steps but android auto still won't open. My phone says it is connected and screen keeps flashing (seems it is trying to open android auto but can't) but on Zlink it just says "connecting".
I also wasn't able to open android auto via usb. Would there be any settings I need to change?
nicchiang9 said:
I've followed these steps but android auto still won't open. My phone says it is connected and screen keeps flashing (seems it is trying to open android auto but can't) but on Zlink it just says "connecting".
I also wasn't able to open android auto via usb. Would there be any settings I need to change?
Click to expand...
Click to collapse
I have the same problem, here's what I do.
-Uninstall android auto
-unpair BT device with Headunit
-Pair your phone with Headunit
-open Zlink app and see if the connecting green arrows in the center are showing... if they are, close the app (zlink) and update or reinstall AndroidAuto... when its done open Zlink and it should work.
IF THE CONNECTING ARROWS ARE NOT SHOWING, no need to close the Zlink app, just update android or reinstall it and it shoul start connecting.
my problem is that after this connection, the next time i get on my car AA wont launch and i need to do this steps all over again...
ALSO, i did What post#12 from lukinha says WITH some EXTRA steps:
Inside android auto cofig I used start android auto autmatically ALWAYS.
once you're developer (clicking android auto version several times) , INSIDE AA configuration...click 3 dots on right upper corner...Developer settings...and in Aplication mode i used programmer... I used my stereo resolution up to 1280 x 780.
i dont know if all of this helps, but i did it anyways.
Now, try to connect and if it doesnt just disconnect wifi and bluetooth and reconect again... android auto will start searching and Zlink app should pair.
HOPE THIS HELPS, IT WORKED FOR ME.
nicchiang9 said:
I've followed these steps but android auto still won't open. My phone says it is connected and screen keeps flashing (seems it is trying to open android auto but can't) but on Zlink it just says "connecting".
I also wasn't able to open android auto via usb. Would there be any settings I need to change?
Click to expand...
Click to collapse
In your case is more easy to solve bro.
1° Enable your 4G, 3G....
2° when zlink has created the hotspot and you are connected to bluetooth, disable your wifi and bluetooth and enable again. wait about 10-15 seconds and Android Auto will appear.
Edit: Added video with instructions... Really sorry for my bad english.
In the minute 1:18 the mic has failed, turn off the wifi and bluetooth and enable again...
I'm having a similar issue of not being able to connect to Andriod Auto via my M.I.C' GT464EA AI Box with Andriod 10. It doesn't use Zlink app it uses "Multiplay". After creating a hotspot on the AI box and connecting to it from my phone's wifi and via bluetooth it says "Connecting" then eventually it stop and hangs on "waiting". i tried turning off wifi, bluetooth, turning them on again but doesn't fix it. On my phone's navigation/tray it says "looking for android auto". The AI box functions are working fine but no matter what i try to do i cant seem to get a connection to Andriod Auto. Would really appreciate any assistance.
zizimanizi said:
I'm having a similar issue of not being able to connect to Andriod Auto via my M.I.C' GT464EA AI Box with Andriod 10. It doesn't use Zlink app it uses "Multiplay". After creating a hotspot on the AI box and connecting to it from my phone's wifi and via bluetooth it says "Connecting" then eventually it stop and hangs on "waiting". i tried turning off wifi, bluetooth, turning them on again but doesn't fix it. On my phone's navigation/tray it says "looking for android auto". The AI box functions are working fine but no matter what i try to do i cant seem to get a connection to Andriod Auto. Would really appreciate any assistance.
Click to expand...
Click to collapse
Tried to rename the hotspot and/or change password on the head unit?
TorstenH said:
Tried to rename the hotspot and/or change password on the head unit?
Click to expand...
Click to collapse
Yes i have and no good.
In saying that i've had to take drastic measures and upgraded the unit from Android 10 to Android 12! still need to mess around with it a bit but will report back results in due course
Hi,
I just managed to get Wireless Android Auto working on my Isudar MNS790ADSP Android 11 Head Unit (PX6, Exact type is NA02R6VW0702)
I have Zlink app version 4.0.41.13:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had to enable "Wireless Auto" in Zlink settings (you have to scroll down in settings to see that option) - it is disabled in default for some reason:
After those settings everything started to just work.
===============================================================================
Another important and kinda undocumented thing is, you have to Install these apps in your phone:
Google: https://play.google.com/store/apps/details?id=com.google.android.googlequicksearchbox
Google Text-to-speech: https://play.google.com/store/apps/details?id=com.google.android.tts
Google Maps: https://play.google.com/store/apps/details?id=com.google.android.apps.maps
With those apps uninstalled/disabled (Like I had) it does not work. Zlink will stay in waiting screen forever while on phone you will experience "Android auto - Searching" (or something like that, I do not remember exactly).