I have recently purchased an Oppo Reno2 Z. One issue that I am having is with connecting phone Android Auto on my Sony AX-5000 car stereo. Android Auto was working on this car stereo with my previous phone (a Nokia 7 plus) without any issues, so I am confident the problem is with the Oppo phone and not the stereo or usb cables I have used. I also have found the odd post from other Oppo users with the same issue.
When connecting the Oppo Reno2 Z (running ColorOS 6.1) to the stereo, Android Auto does not start up and instead I get the message 'USB device not supported'. I am able to get Android Auto to work by initiating Developer Options on the Oppo and then changing 'Select USB Configuration' from 'Charging' to 'MTP (Media Transfer Protocol)', however this only works for that one time and next time I try to use Android Auto again I am forced to go through the above steps once again. It does not appear that it is possible to permanently change USB Configuration to MTP (Media Transfer Protocol).
Does anyone know of a permanent solution to this issue? I'm hoping that it may be fixed in ColorOS 7, however that is not yet available in Australia for this phone.
Many thanks in advance.
Related
I am one of the lucky people who will get a car with the ability to connect my smartphone to it using Mirrorlink or Android auto.
Anybody here who has tried to connect their nubia z7 mini with Android Auto or Mirrorlink? Is it even possible?
I am currently running Mokee 6.0.1 which is Android Marshallow so I am pretty confident Android auto should work.
So, is anybody using Android Auto with the Nubia z7 mini and if so, which ROM are you using and is it working well?
Since nobody could answer me and I now had the chance to test it, I can confirm that Android Auto works on the Nubia Z7 mini.
I am using Android 6.0.1 from Mokee (MK60.1-nx507j-201604060258-NIGHTLY) and everything works out of the box with no bugs or problems.
Don't know if anybody is interested in this but I can as well share the information since it might be useful someday to somebody .
Get Nubia to work with mirrorlink
Hi, i see that you've managed to get your nubia phone to work with mirror link. I was just wondering if u could help me?
I understand my phone is Nubia z11, a bit different from yours but i was wonderring if there is anyway i can make mirror link in my car to recognise my Nubia z11?
Ive downloaded android auto into the phone but whenever i connect my phone to my car using USB it just keeps saying that it doesn't recognise the device or device not detected. Is there anything i can do to make my car recognise the phone?
Thank you
First of all, there is a difference between mirrorlink and Android Auto. Mirrorlink is a technology that mirrors your phone screen on your car and works with most older car models. Android Auto was developed by Google and your car needs support for Android Auto to make it work.
Mirrorlink has never worked for me but since I can use Android Auto, I never really bothered to try so I cannot assist you with mirrorlink .
For Android Auto I can only suggest you to google everything you can find about it and as far as I have experienced, there are a couple of tricks you can try that solve AA problems in 80% of the cases
1. Use a high-quality USB cable
2. Enable the Media Transfer Protocol on your phone
3. Make sure that your time and date is set correctly on your car.
4. Check if Android Auto works correctly on your phone before connecting it to your car
5. Make sure google play services is installed correctly
6. Check if the bluetooth connection is on
All I can say is good luck since AA is sometimes a real pain in the ass
No android auto works fine but it's getting it to show up on my new car's monitor screen !!! ??????
Is there anyone success in connecting this phone to a car using "Android Auto" ? I try many roms in the kenzo development section but none of them makes the phone being detected by the car through USB. I had another Mi Note Pro on the CM13 rom and the phone is connected to the car through USB cable.
on my note 2 i have to connect the phone and then activate thhe MTP protocol. it gets deactivated automatically a few seconds later. after that android ajto works perfectly good. maybe this will help you
I know this is an old thread but any solution?
So, I have an issue with audio out via USB. On android 7, I would plug an USB into the car headunit connecting it to the phone. In android 8, it doesn't recognize the device. The phone keeps disconnecting, shows android accessory connected, then it disconnects again until the HU throws an error
S7 Edge Exynos running Android 8.0.0 ERC6
Up. I've read somewhere that it has something to do with AOA, and that's not supported in Oreo. Is this the case ?
Same problem here. I've managed to get it working by forcing 'Audio Source' option under USB connection settings in Developer Options, but it has to be manually set each time. So if the head unit or connection freezes (which does happen), you have to physically reconnect and start from scratch. Which can't be done safely whilst driving...
I can't get Android Auto or Mirror Link to work on my Skoda Kodiaq, it's not the car as all other phones work with it. I have tried using the stock cable and other cables, when i connect it, the car recognises something is connected and the phone asks me what to do with the USB connection (charge only, transfer files or photos) and i've tried all of them. The car eventually gives up and says the phone is not compatible, something i used to get with my OnePlus 3t as it didn't support Mirror Link but it would work instantly on Android Auto.
I have read online that there were issues with Android Auto on previous phone models but the manufacturer were looking to get this fixed in this phone. If it was a cheap phone i'd probably just leave it, as i did with Mirror Link on the OnePlus, but for a phone they are pushing at a crazy price and saying is premium, they have work to do. Has anyone figured out any fixes for this, or managed to get it to work on their car?
I've got the same problem with my huawei mate 20 pro and Dynavin 7 ce in Tuareg.
Very annoying thing. Any solution someone?
I have a 4 week old T-Roc and Android Auto works fine on mine, I can't quite remember what options I had to allow on the phone but it didn't work straight out the box but works fine now with Google Maps, Waze and Spotify.
There was a bug with some cars and newer android versions. I have to enable USB debugging on my phone for android auto to work. Can't explain why.
Ive been using it for a few days and have no issues with Google map, listening to music or making calls or sending texts using voice.
Does anyone know how to stop it asking what you want to do everytime you plug in the usb in the car? Very annoying.
Anyone noticed that Mi Pad 4 64+4 Wifi could not recognize any MIDI device?
I have already tested the device in both MIUI and Stock Android, adjusted developer mode USB connection settings, still cannot work.
I tried on a Google Pixel and it worked flawlessly, I saw two posts in official MIUI forum reporting the same problem too, so I guess this is a hardware problem? Maybe XiaoMi has to do some update patches to enable the function?
APP: Cross DJ Pro / Unipad
MIDI hardware: Serato DDJ SB, Launchpad.
If anyone has any knowledge to help, I am much appreciated.
I just received mine yesterday, and met the same problem, can't recognise elec piano and fhis was the main purpose I bought t it for... Will ring the customer service later today see what happen. (Btw, xiaomi Mix 2s works fine with MIDI, DID NOT EVEN CHANGE THE CONNECTION MODE)
Same issue here. I have Caustic 3 and FL Studio Mobile. Both work fine with my Pixel 3, and my old tablet (Galaxy Tab 4) but the Mi Pad 4 doesn't seem to recognize the midi devices being plugged in (other devices ask for permissions when it is plugged in but the Mi Pad 4 never asks). There is a developer option as to what to default the USB connections to. I changed that to MIDI but that still didn't make the midi devices show up in Caustic or FL Studio Mobile. If anyone knows if there is a fix for this, it would be greatly appreciated.
I had same problem. It was fixed by using proper USB C OTG cable. Micro USB OTG with some kind od additional micro -> USB C adapter (probably charging only) did not work.