I'm having trouble with my M7 with connecting to my pioneer AppRadio.
The problem started when I updated to Viperone 7.0.2 rom which included updating the firmware. Before that I was using the previous version of Viperone and had no issues, using the Appradio Unchained app. Now, when I connect the phone to the MHL cable I get an error on the stereo saying that the USB connection has been disabled for device protection and the connection shown on the phone constantly connects and then disconnects.
I thought the problem was with the app but I've uninstalled that and the connection still loops so I think there is some issue with the phone rather than the app.
I'm kind of lost as to where to start! Any ideas?
MrPez said:
I'm having trouble with my M7 with connecting to my pioneer AppRadio.
The problem started when I updated to Viperone 7.0.2 rom which included updating the firmware. Before that I was using the previous version of Viperone and had no issues, using the Appradio Unchained app. Now, when I connect the phone to the MHL cable I get an error on the stereo saying that the USB connection has been disabled for device protection and the connection shown on the phone constantly connects and then disconnects.
I thought the problem was with the app but I've uninstalled that and the connection still loops so I think there is some issue with the phone rather than the app.
I'm kind of lost as to where to start! Any ideas?
Click to expand...
Click to collapse
Revert back to the previous version and see if the problem persists. If it does, then it might be the phone; if not, then it is the ROM.
majmoz said:
Revert back to the previous version and see if the problem persists. If it does, then it might be the phone; if not, then it is the ROM.
Click to expand...
Click to collapse
That was the only thing I could think of. Was hoping for something a little less drastic though!
I know this might be a lost cause but I will ask anyway. I had my watch and loved it(still do) but since getting the Pixel XL I have had issues. These are the steps I have taken so far.
1. turned both watch and phone on and turned on bluetooth
2. watch connected to phone and reset itself
3. connected to phone via bluetooth and got the passkey (stated it would be phone audio only)
4 launched the gear manager and it tried to find it but would not (even though the bluetooth did)
5. downloaded the XDA gear manager and installed it on the phone but it force closes each time.
So anyone else with similar issue? I suspect it is the app version not being for android 7.1 or the fact the watch is no longer compatible with other devices anymore (hopefully not).
Any help is greatly appreciated on this subject.
Thank you All.
I have a friend who is having the same issue, Gear 2 on the Pixel XL. We put the app on the phone, reset the watch, but I can't connect the two. Bluetooth connection seems to work, but the app doesn't pick up where it needs to in order to complete the process. He came from a Note 4 (with a Note7 in between). I have an S2 watch I need to try this on as well, but I figure I'll likely have the same issue. Eagerly awaiting an update to fix this!
stud421 said:
I know this might be a lost cause but I will ask anyway. I had my watch and loved it(still do) but since getting the Pixel XL I have had issues. These are the steps I have taken so far.
1. turned both watch and phone on and turned on bluetooth
2. watch connected to phone and reset itself
3. connected to phone via bluetooth and got the passkey (stated it would be phone audio only)
4 launched the gear manager and it tried to find it but would not (even though the bluetooth did)
5. downloaded the XDA gear manager and installed it on the phone but it force closes each time.
So anyone else with similar issue? I suspect it is the app version not being for android 7.1 or the fact the watch is no longer compatible with other devices anymore (hopefully not).
Any help is greatly appreciated on this subject.
Thank you All.
Click to expand...
Click to collapse
I would like to know if there's a solution to this as well. I upgraded from a Note 4 and haven't had any luck getting my Neo to show up in Gear Manager for my LG V20.
I came from an S4 and had the exact same issue as stated. It will connect through bluetooth devices, but the Gear Manager app refuses to find or acknowledge it exists.
I suggest doing a factory reset. I have to do a reset every time I flash a new rom on my phone. I have to do this on both the tizen rom and android wear.
Has anyone figured out how to connect pixel XL to the gear neo 2? I am having the same problem. Can connect to watch with Bluetooth, but will not connect through the app.
Thanks for any help.
have any of you with this problem flashed android wear to the gear 2 neo? i use it as a daily driver and its very stable, might be the solution for your issues
Had it but lost it
I had my pixel XL connect to a flashed gear2 Neo
I reset my phone and know no matter what I try it won't connect this happened at the same time they updated Android Wear. W os . I installed an old version of Android Wear could not connect I flashed different roms
I'm giving up
Hello, a fellow 3T owner here!
Just installed the latest OxygenOS 5.0.1 update and after that I am unable to cast my screen to my cars screen via Miracast. I am able to connect to my car via Wi-Fi but after turning "Cast" on I get the error message: "Connected, no internet". Before the update everything was working fine.
Does anybody have a similar issue? Any solutions?
Thanks!
Have you tried casting to another smart display? Something like your Laptop/PC? On Windows 10, search for the Program "Connect" and use the same way to connect to it.
Why? To nail down where the issue may be, in your phone or your Car Screen. Also, try using another Miracast Compatible device to connect to it.
Miracast
I was having the same problem...EZMira app (Playstore) works like a charm for me
Hello,
Maby not the first question.
Someone can tell me about Android auto and Mi A2 (Stock Pie)?
Not working on Opel Corsa 2016...
Thanks!
With stock pie, Android Auto is ok for me on Kia Rio. I don't test on Opel.
Anyone else???
For what its worth since this thread is a few months old I cannot get my Mi A2 to connect to my Android Auto head unit. It runs on the phone will auto start when it BT to the car but the head unit just doesn't see it. Have tried different usb cables, cleared the cache but have not done a full reset of the phone because too much effort. The phone is on Android 9 with the latest security updates. Waiting to see if Android 10 will fix it.
It seems it is a known issue with many reports on both the Android Auto forums as well as the Xiaomi forums. Haven't tested with another car or phone (got new car and new phone at pretty much the same time).
Although my connection has been working lately I did initially have issues.
I had some success getting my car (Suzuki Ignis) to recognise the phone by doing the following.
Plugging phone into car.
Clicking the USB options notification.
Changing it from charging to file transfer.
It would then flip back to charging automatically and the car would recognise the phone as an Android Auto device.
I have a Galaxy S9+ using a sony head unit. Since the android 10 update most things dont work anymore. Samsung doesnt respond to questions and either does google. I would roll back to 9 but my bootloader is locked. Is there anyway around this ?
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
mrdlejzr said:
I ran into 2 problems after upgrading to Android 10 on my S10e.
1. I had second AA app installed (I think it was the one for phone display)
2. Adb debug has to be off
Also app settings are accessible only through Settings -> Apps -> AA -> In-app notifications settings
Click to expand...
Click to collapse
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
uhi711 said:
This is because AA is built-in into Android 10, it is part of the operating system, so there is no need for the AA app. Upgrading to Android 10 should automatically remove the AA apk used on Android 9.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
I uninstalled the old aa app on my phone because i thought it was part of the os, restarted the phone and plugged it in my truck and it would not connect. The only way aa almost works is if you install the app on your phone.
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
uhi711 said:
As I said before, AA is built-in in Android 10, so there is no need for the apk. But you are right, there are still a lot of problems with AA on car's screen and Android 10. The fact that your phone does not connect to your car's infotainment system or that you are able to sometimes use AA after installing the apk, does not mean that it should be like this. I am sure that you sideloaded the apk because it shouldn't appear on your Play store after upgrading to Android 10.
I, for example, I refused to upgrade because of the many bugs I read about when using AA. I suffered enough (repeated connection problems), in the beginning, after upgrading my phone from the Note 8 with Android 8 to the Note 10+ with Android 9. I'm afraid that it is not possible to go back to Android 9, as far as I know. You'll have to stick with what you have and dig the internet to find possible solutions, because I'm sure there isn't yet a straight forward fix for your AA problem.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
dinosaurus1 said:
So i uninstalled AA from my phone and then restarted it. Then i backed it up with smart switch, i then did a factory reset. Then i did a clean install of 10 from Chimera. I restored my phone and plugged it into my truck. It proceeded to install AA and still not worth a damn lol. That was a good 3 hours not well spent. So now i will play no more until if ever a fix comes out. Thanks
Click to expand...
Click to collapse
Sorry to hear about all the trouble. Just keep searching the internet about your specific problem and configuration. If you still have your previous phone and if it still has a working AA, you could use it just in your car connected to your wifi hotspot from your Note 10. Also try a different cable, a shorter one (I use a 1 foot only cable), all my connection problems went away with this shorter cable bought on Aliexpress. Wish you luck!
Sent from my SM-N975F using Tapatalk
---------- Post added at 07:59 PM ---------- Previous post was at 07:50 PM ----------
I forgot to ask, did you try using AA with a wireless connection? If you have a new car, chances are that you could use wireless connection between your phone and the car. There is a setting in AA to enable this. Just set this switch on before trying to connect to the car's infotainment system.
Sent from my SM-N975F using Tapatalk
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
deepudips said:
@uhi711 what did you do to resolve the issues on note 10+
Since Samsung updated to android 10, my AA has not worked.
Cables are same that used to work on Android 9
Keeps disconnecting and reconnecting
Tried clear cache and data on AA
Reset the cars head unit
Used new cables, old cables, OEM cables same issues
Haven't tried a small cable, will try the charger cable that comes with Sony xm3 head phones
Click to expand...
Click to collapse
Unfortunately, I do not have a satisfactory answer for you. I just didn't upgrade my phone to Android 10, because of the many bug reports I read about. A long time ago, when I was using the Note 8 and Android 8, I had the same connection problems for a few months. Then, the only thing that helped me was using short (20-25 cm) quality cables, bought on Aliexpress. It might also be a coincidence, I'm not sure, because in the same time I changed cable after cable, Google also updated AA. As of now, I'm using the Note 10+ with Android 9 and the same short cable that I think it fixed my connection problem then, and I still don't have any problem. You'll just have to wait patiently for Google to fix the bugs.
Sent from my SM-N975F using Tapatalk
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
woody4165 said:
Hi
I have Lineage OS 17.1 which is Android 10.
Should I install just "AA for phone" instead of normal AA ?
With "normal" AA installed is working, except for notifications that I don't get for any apps (Whatsapp, Telegram,...)
Thanks
Click to expand...
Click to collapse
I'm sorry, I'm afraid I can't help you. I don't know what is Lineage OS and how it works. What I do know is that there is no such a thing as different AA versions. There is only one kind of AA app downloadable from the Play store if you have Android 9 or less on your phone. If you have Android 10 installed on your phone, then you do not need the AA app and you won't be able to download it from the Play store, because it is already built-in in the OS (Android 10).
Sent from my SM-N975F using Tapatalk
I had the same problem with my Note 9 with Android 10, it kept connecting and disconnecting. Restarting the phone worked for me.
The couple AA and Android 10 is known for a lot of bugs and connection problems.
Sent from my SM-N975F using Tapatalk