Hi all,
I just got a JVC KW-V830bt head unit installed. I installed aa auto latest version, aa mirror and aa unlock. I've installed all three apps and I'm not getting the aa mirror option in my head unit. Is there something I'm doing wrong? aa unlock has root permission in magisk. AA and aa mirror are not listed in magisk. I have developer mode on in aa and checked unknown sources. I rooted my phone and got this head unit so I could mirror my phone and no joy. Can anyone help?
I have the a
Same raido too have you made any Progress on rooting it
Did you resolve the problem?
pilot60378 said:
Hi all,
I just got a JVC KW-V830bt head unit installed. I installed aa auto latest version, aa mirror and aa unlock. I've installed all three apps and I'm not getting the aa mirror option in my head unit. Is there something I'm doing wrong? aa unlock has root permission in magisk. AA and aa mirror are not listed in magisk. I have developer mode on in aa and checked unknown sources. I rooted my phone and got this head unit so I could mirror my phone and no joy. Can anyone help?
Click to expand...
Click to collapse
I have the same problem. Please give me a suggestion.
Thanks,
Beniamin
I have got mi 8.when i started application ibsaw bkack screen.İ enter screen settings s2auto i choose 0 değere screen iş working.After i choose 90 degree the screen is working horizantally.
When i try after 1 hour i do ağacın same process.how can i solve?
Related
Hi folks,
i ve been experiencing Android auto connection issues.
Want to connect to Skoda car infotainment from my rooted htc one V(CM 12.1 - Lollipop 5.1), but unfortnatelly havent had luck so far.
Downloaded newest AA apk, but it won´t even let me start the app. So I tried the older version (1.2.084954_2166577-release) of AA with successfull start. However, the only thing I see is the initial screen(see attachment), nothing else. Even after USB connection the infotainment display gives me "not compatible USB" warning. Have tried all MTP, PTP and only charging connection modes.
Is there something Im doing wrong? Is there any other way I can get this running?
Cheers for all ideas and comments.
I am almost in same situation!
Hi,
I used to be able to launch android auto on my galaxy s6 Skoda Fabia 2016. It also used to work with a galaxy s4.
About a month ago (or more), it stopped working:
When I connect the phone, AA is launched but the exists and the USB connection is reset. I can see in my task manager that AA is active in background.
I can connect with MirrorLink, but I rather use AA.
The car didn't go through any upgrades so I guess the blame is at AA.
I tried replacing USB cables, resetting the AA on my phone, changing USB connection from MTP to all other possible options... nothing helps.
Any ideas?
AA found that new version is available, but you are somehow frozen during inicialization.
Please provide following info:
1. AA version (go to Application Manager -> current is 1.6.281040
2. in Application manager press FORCE STOP for AA. If you have any cash data for AA, remove it
3. (OPTIONAL). IN skoda HeadUnit, go to settings -> Factory Reset -> Navigate to FUllink/SkodaLink/Whatever link and have reset of AA/Mirrorlink
4. check in mobile, that AA is not running. If yes, clear it from memory!
5. connect via USB, go to Headunit and launch Android Auto. You should go thru setup phase and everything should work.
Fast check if you need update of AA:
Launch AA application, if you see Update/Upgrade banner, you need to perform above. If you are unsure, create a screenshot and i can advise.
Mgx
skfree said:
AA found that new version is available, but you are somehow frozen during inicialization.
Please provide following info:
1. AA version (go to Application Manager -> current is 1.6.281040
2. in Application manager press FORCE STOP for AA. If you have any cash data for AA, remove it
3. (OPTIONAL). IN skoda HeadUnit, go to settings -> Factory Reset -> Navigate to FUllink/SkodaLink/Whatever link and have reset of AA/Mirrorlink
4. check in mobile, that AA is not running. If yes, clear it from memory!
5. connect via USB, go to Headunit and launch Android Auto. You should go thru setup phase and everything should work.
Fast check if you need update of AA:
Launch AA application, if you see Update/Upgrade banner, you need to perform above. If you are unsure, create a screenshot and i can advise.
Mgx
Click to expand...
Click to collapse
Thanks for the instructions but it didn't help
My AA version is 1.6.281040. No update\upgrade banner when I open the app.
I tried all of the above steps (force stop + clear data and cache + factory reset my car smartlink) but the result is the same:
When I try to connect the car- AA launches and immediately goes to the background and the connection fails.
Any other ideas?
How can I debug this?
questions
Hi,
1. before launching AA, is bluetooth on your phone activated and you are paired with Skoda HeadUnit? You should be able to make a call via HeadUnit with buttons on wheel/buttons on headunit. Working bluetooth connection is mandatory prereq for working AA yet (USB cable is just not enough)
2. USB cable - i have seen situations, when setup has been not working with long cable or chinese fake cable. Try to use short original factory cable 0.3m maximum from Samsung (should be white), this works
3. what ROM are you using? Its original rom from SAMSUNG? If yes, please indicate build number+version. If not, this may be problem as non-original rom doesn't support DPIchange yet.
4. You can enable devel mode. enable usb debugging on android side + in AA - follow http://www.androidexplained.com/android-auto-developer-mode/
5. do you see on mobile at least ANDROID AUTO label for second?
6. where are you located? S6 is oficially supported phone on SkodaHU, so you may also ask support from importer via dealer.
Hey,
over at the Mazda headunit project, with a opensource custom AA, there is problems too. It appears that a new version of "Google Play Services" broke AA.
Play services is a sort of API that broker things like GPS and USB for apps.
Last working version is 9.0.83. Your timeline fits with the issue of the affected versions. Please send a bug report to Google to get them to fix it : [email protected]
larxxor said:
Hey,
over at the Mazda headunit project, with a opensource custom AA, there is problems too. It appears that a new version of "Google Play Services" broke AA.
Play services is a sort of API that broker things like GPS and USB for apps.
Last working version is 9.0.83. Your timeline fits with the issue of the affected versions. Please send a bug report to Google to get them to fix it : [email protected]
Click to expand...
Click to collapse
That email just gives us a bounce back not sure if google receives you but you guys should post here!
https://productforums.google.com/forum/#!topic/play/tflL2_GCj4s
skfree said:
Hi,
1. before launching AA, is bluetooth on your phone activated and you are paired with Skoda HeadUnit? You should be able to make a call via HeadUnit with buttons on wheel/buttons on headunit. Working bluetooth connection is mandatory prereq for working AA yet (USB cable is just not enough)
2. USB cable - i have seen situations, when setup has been not working with long cable or chinese fake cable. Try to use short original factory cable 0.3m maximum from Samsung (should be white), this works
3. what ROM are you using? Its original rom from SAMSUNG? If yes, please indicate build number+version. If not, this may be problem as non-original rom doesn't support DPIchange yet.
4. You can enable devel mode. enable usb debugging on android side + in AA - follow http://www.androidexplained.com/android-auto-developer-mode/
5. do you see on mobile at least ANDROID AUTO label for second?
6. where are you located? S6 is oficially supported phone on SkodaHU, so you may also ask support from importer via dealer.
Click to expand...
Click to collapse
Bluetooth is working and connected to the car.
I tried several different USB cables (originals and non-originals) but none helped.
I'm using stock rom: 6.0.1 build number MMB29K.G920FXXU3DPEK
5. do you see on mobile at least ANDROID AUTO label for second? I see AA launches and then it moves to the background. I don't see the "Android auto" overlay that was usually there.
I'll try contacting Skoda representative but since nothing has changed in the car unit, I believe it's a software issue in the phone.
soulz said:
That email just gives us a bounce back not sure if google receives you but you guys should post here!
https://productforums.google.com/forum/#!topic/play/tflL2_GCj4s
Click to expand...
Click to collapse
Sounds like my issue. I posted in the forum link.
After reading through he posts in @soulz link, I found a solution:
https://productforums.google.com/d/msg/play/tflL2_GCj4s/Y5Ens5WxBwAJ
Basically, I disabled the following services:
ReschedulerUsingAlarmManager
ReschedulerUsingBroadcast
This needs root! but it works like a charm.
Now, all that's left to do is wait for Google to fix the play services issue.
Does Android auto work for anyone else?
I get no indication it's detecting it. I've tried the cable that came with and a third party
It works fine with a OnePlus 5
I'm on version 10.3.1
Ollie_17 said:
Does Android auto work for anyone else?
I get no indication it's detecting it. I've tried the cable that came with and a third party
It works fine with a OnePlus 5
I'm on version 10.3.1
Click to expand...
Click to collapse
Fixed, deleted app and turned on usb debugging and it's working
Ollie_17 said:
Fixed, deleted app and turned on usb debugging and it's working
Click to expand...
Click to collapse
Hello, have similar problem - my android auto look it is working, but i think that is not working properly. I have a screen, with all apps, but spotify dont work, waze looks working, but GPS dont, after disconnecting cable it comes with error 16.
Also i have no Android auto between APPS screen - is it OK ?
I'm on MIUI 11.0.3,
thanks for have a look
Ollie_17 said:
Fixed, deleted app and turned on usb debugging and it's working
Click to expand...
Click to collapse
I am on xiaomi.eu ROM V11.0.3.0.QFKCNXM_v11-10 (Android 10) and my Andoid Auto is not working.
I tried:
- with installed APP "Android Auto" --> "no connection possible" shown on car display
- without APP --> RED error 8 on phone display
USB Debugging is enabled
Is it better with Android 10 not to install the APP as it should be built into system ?
What else could I try ?
Car: (Skoda fabia 2020, with swing smartlink) on MI9T Pro. Same error, 8. MIU 11, Android 10. Installed Android auto apk from apkmirror, but not showing up as icon. In car, always error 8, time/date. Did a softreboot of radio in car, meaning hold on/off for 10 seconds, after reboot it all worked and now reconnects without problem. Android auto apk from apkmirror I would not do again. Please also set USB debugging to on, have a feeling this is also a problem when off. Then lastly, make sure you have no dual apps, delete these as this is also a known problem.
Hi. I have managed to connect my Android radio with the Carlink accessory, but the Android Auto screen in my car is pixelated. The texts can hardly be read. What can be? Thank you
I wish to figure out if it's possible to change AA DPI when phone is connected to head unit.
With AA wireless, when you change DPI, it's possible to get a splitted screen, but i wish to know if it's possible to do it with a wired connection?
Regards
huck3301 said:
I wish to figure out if it's possible to change AA DPI when phone is connected to head unit.
With AA wireless, when you change DPI, it's possible to get a splitted screen, but i wish to know if it's possible to do it with a wired connection?
Regards
Click to expand...
Click to collapse
There already is one for wired connections. Use it all the time. Works great.
[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto
Update 30.11.2022 End of life and open source. Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source. Code is accessible...
forum.xda-developers.com
heffer86 said:
There already is one for wired connections. Use it all the time. Works great.
[APP][5.0+]OBD2 Plugin for Android Auto - Use Torque with AndroidAuto
Update 30.11.2022 End of life and open source. Due to lots of changes both in Android and in my life, I do not have the possibility to maintain / update the code any further, therefore I've decided to open source. Code is accessible...
forum.xda-developers.com
Click to expand...
Click to collapse
Would you be willing to share what setup/versions you're using that is working? It seems like OBD2AA isn't working on newer AA versions, at least for me anyways. I've spent way too much time on it as a project haha.
I've got a 2022 VW Golf R (MIB3) and have tried with a Pixel 6 Pro on A12L and a OnePlus 6T on A9. Every time I select OBD2AA when connecting to my car the head unit will bring up a black screen as though it's about to show AA, but just goes back to a prior menu on the car and OBD2AA just crashes (on both phones). I tried patching the app via AA AIO Tweaker as well.
Tried older versions of AA on the 6T and even if I can get around the app requirements being out of date, AA just throws error 14 and wants me to update Play Services. So I've been a bit stuck with it unfortunately.
MINISPOON939 said:
Would you be willing to share what setup/versions you're using that is working? It seems like OBD2AA isn't working on newer AA versions, at least for me anyways. I've spent way too much time on it as a project haha.
I've got a 2022 VW Golf R (MIB3) and have tried with a Pixel 6 Pro on A12L and a OnePlus 6T on A9. Every time I select OBD2AA when connecting to my car the head unit will bring up a black screen as though it's about to show AA, but just goes back to a prior menu on the car and OBD2AA just crashes (on both phones). I tried patching the app via AA AIO Tweaker as well.
Tried older versions of AA on the 6T and even if I can get around the app requirements being out of date, AA just throws error 14 and wants me to update Play Services. So I've been a bit stuck with it unfortunately.
Click to expand...
Click to collapse
I am running a Pixel 5 on Android 12 with Ford Sync 3 and 4. I have the latest version of AA also. Do you have the torque pro app? Did you pay for the app on the website in the post? You can't just use the one found in the app store. You don't need a rooted phone for it to work.
My suggestion would be to clear out the app data for Android Auto and clear out the app defaults. I would then reboot your phone. While the phone is un-locked plug your phone into your headunit. Hopefully you will get the prompt to select Android Auto or OBD2AA.
heffer86 said:
I am running a Pixel 5 on Android 12 with Ford Sync 3 and 4. I have the latest version of AA also. Do you have the torque pro app? Did you pay for the app on the website in the post? You can't just use the one found in the app store. You don't need a rooted phone for it to work.
My suggestion would be to clear out the app data for Android Auto and clear out the app defaults. I would then reboot your phone. While the phone is un-locked plug your phone into your headunit. Hopefully you will get the prompt to select Android Auto or OBD2AA.
Click to expand...
Click to collapse
Thanks for all that info, I appreciate the reply. I've got both apps and ensured Torque Pro is communicating properly as well. I'll try clearing everything for AA, I had been doing that with the other apps instead thinking that was the issue but never thought to try it with AA itself.
Coolwalk AA UI is rolling out as a public beta right now Seems that beta channel is full, but APK should soon be available at ApkMirror
Android Auto's long-awaited redesign is nearly here — here's how you can take it for a test drive
Which version are you in ?
I think it's still a server side thing sadly for non beta members
It's a server-side switch, so even if you have the latest beta apk, it won't help.
RaZor83 said:
Which version are you in ?
I think it's still a server side thing sadly for non beta members
Click to expand...
Click to collapse
Yes, you have the point here, it's a server side.
I'm at latest beta, and I've tried rebooting phone and clearing AA cache, but still no coolwalk interface on both wired and wireless AA.
Anyhow, this is last phase of testing, and we should soon have it
Still hope to get it public before 2023
If you set the flags with root now. Will they reset?
cammykool said:
If you set the flags with root now. Will they reset?
Click to expand...
Click to collapse
I have set them on saturday.... still works!
HofaTheRipper said:
I have set them on saturday.... still works!
Click to expand...
Click to collapse
What all did you enable to get it working? Just following OP and it doesn't reset?
cammykool said:
What all did you enable to get it working? Just following OP and it doesn't reset?
Click to expand...
Click to collapse
did the termux commands and it still works.
Thread 'Google Cast & "Coolwalk"' https://forum.xda-developers.com/t/google-cast-coolwalk.4396533/
before google released it to beta, it reseted after 1 day... now it works since 3 days
unfortunately, it got reseted today :-(
Become a beta tester, go to settings, apps, android auto: click on the three dots upper right side of the screen en select 'uninstall updates'. Reboot the phone and update android auto to the latest available version. Connect to the car, setup android auto and disconnect from the car/headunit again. Reboot your phone once more and android auto is 'Coolwalk" when connected again.
Worked for me on a Oneplus 10 Pro with the latest Oxygen 13 OS, headunit in the car is an aftermarket Kenwood DMX8019DABS,
Works for a day then just reverts back, can't seem to make it stick.
[email protected] said:
Become a beta tester, go to settings, apps, android auto: click on the three dots upper right side of the screen en select 'uninstall updates'. Reboot the phone and update android auto to the latest available version. Connect to the car, setup android auto and disconnect from the car/headunit again. Reboot your phone once more and android auto is 'Coolwalk" when connected again.
Worked for me on a Oneplus 10 Pro with the latest Oxygen 13 OS, headunit in the car is an aftermarket Kenwood DMX8019DABS,
Click to expand...
Click to collapse
That did not work for me. Probably because I'm not a beta tester and I've been trying to become one for years. That's with the latest daily build on 11.21.2022
I'm an Android Auto beta tester and my issue is that if I reboot my phone then connect to my car, Coolwalk UI will load, then if I connect to my car again a few hours later it loads back the old AA UI.
Any ideas why?
Same problem here, this beta coolwalk rollout is a complete disaster!
Cyclops1055 said:
I'm an Android Auto beta tester and my issue is that if I reboot my phone then connect to my car, Coolwalk UI will load, then if I connect to my car again a few hours later it loads back the old AA UI.
Any ideas why?
Click to expand...
Click to collapse
For me as beta tester Coolwalk keeps working, also after multiple reboots. I'm also beta tester for the Google app, Waze and Maps. I'm on Oxygen 13 (Android 13). Not sure what makes the difference compared to your situation.
[email protected] said:
For me as beta tester Coolwalk keeps working, also after multiple reboots. I'm also beta tester for the Google app, Waze and Maps. I'm on Oxygen 13 (Android 13). Not sure what makes the difference compared to your situation.
Click to expand...
Click to collapse
Here is what I have done to get Coolwalk working again, do note that I am an Android Auto beta tester.
I went into Settings>apps>Android Auto
Force stop Android Auto
Cleared data
Uninstalled updates
Installed latest Android Auto beta version (8.6.1246) from Apk Mirror
Reboot phone
Installed latest Android Auto beta version (8.6.1246) again
Connected to car and AA Coolwalk UI has loaded
Disconnected from car
Waited 30 minutes and reconnected to car
Coolwalk UI still loaded
I will see in about 2-3 hours if it sticks
**So I tried AA after 2.5 hours and AA loaded the old UI
Cyclops1055 said:
Here is what I have done to get Coolwalk working again, do note that I am an Android Auto beta tester.
I went into Settings>apps>Android Auto
Force stop Android Auto
Cleared data
Uninstalled updates
Installed latest Android Auto beta version (8.6.1246) from Apk Mirror
Reboot phone
Installed latest Android Auto beta version (8.6.1246) again
Connected to car and AA Coolwalk UI has loaded
Disconnected from car
Waited 30 minutes and reconnected to car
Coolwalk UI still loaded
I will see in about 2-3 hours if it sticks
**So I tried AA after 2.5 hours and AA loaded the old UI
Click to expand...
Click to collapse
same happened to me... also beta tester.... but:
-- clear cache of AA
-- reboot phone
-- start headunit server in AA settings (dev has to be activated)
-- keep headunit server running
As long as i connect to my car with headunit server running, coolwalk keeps enabled for me since 4 days now.
I didnt notice any additional battery drain.
I
HofaTheRipper said:
same happened to me... also beta tester.... but:
-- clear cache of AA
-- reboot phone
-- start headunit server in AA settings (dev has to be activated)
-- keep headunit server running
As long as i connect to my car with headunit server running, coolwalk keeps enabled for me since 4 days now.
I didnt notice any additional battery drain.
Click to expand...
Click to collapse
I tried your suggestion and Coolwalk UI loaded, I will see if it will still load again tomorrow.
I've experienced this AA UI roll back to the old one. But after cleared the cache and rebooting the phone it turns back to cool walk UI until now.
This problem appears when I'm using the wireless AA adapter/dongle (Carlinkit CCPA), finally I'm installed a Head Unit Reloader on my HU (it's a Pioneer Android) and works perfecly without adapter.
Also it still showed cool walk UI when I connect my phone to my other car that use an OEM Toyota Head unit with wireless AA adapter (Carlinkit CP2A).
Maybe its a adapter/dongle firmware compatibility issue triggered the AA to roll back to the old one...