Hi everyone
I got my oneplus 3 after long journey with Note 2,3,4 and after the probmem of the 7 edition i decided to try oneplus 3 and i found it awesome
But the problem is
When connecting my mobile to my car (Mazda CX9) i cant browse my media over Bluetooth also no metadata appears on the car screen although it worked fine with l the note devices, iphone and lenovo
I contacted the support and after many trials we decided to wipe the phone and make system restore
The first time i connected it to the car every thing works fine
Then it comes back to the same problem and just appeared on the car screen as connected
I decided to try Freedom OS
And rhe same thing happened
Worked for the first time
Then just connected
Can any one help solving this
Or can i install any thing which may help
Sent from my ONEPLUS A3003 using Tapatalk
ali.alboghdady said:
Hi everyone
I got my oneplus 3 after long journey with Note 2,3,4 and after the probmem of the 7 edition i decided to try oneplus 3 and i found it awesome
But the problem is
When connecting my mobile to my car (Mazda CX9) i cant browse my media over Bluetooth also no metadata appears on the car screen although it worked fine with l the note devices, iphone and lenovo
I contacted the support and after many trials we decided to wipe the phone and make system restore
The first time i connected it to the car every thing works fine
Then it comes back to the same problem and just appeared on the car screen as connected
I decided to try Freedom OS
And rhe same thing happened
Worked for the first time
Then just connected
Can any one help solving this
Or can i install any thing which may help
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/usb-phone-connect-in-mazda-6-2015.457714/
https://forums.oneplus.net/threads/one-plus-3-bluetooth-phone-support-issue-2016-mazda-cx5.458807/
The 3.2.6 changelog says they fixed the issue
Apparently it works on CM13 or an with app called Bluetooth file transfer
Thanks for your reply
I tried oxygen 3.2.7
Freedom 1.6.1 built in 3.2.7
Regarding CM didn't try it and iam not sure if i will try it
But fir sure will try the app
Sent from my ONEPLUS A3003 using Tapatalk
Bluetooth file transfer didn't work
Sent from my ONEPLUS A3003 using Tapatalk
HI Guys,
Looking for some help.
I have an HTC U11 on Oreo. Recently installed a Kenwood 7704S Android Auto HU.
Installed Android Auto app via google play, as well as latest version direct from Google. Phone is just not detected using the original USB C cable BUT the phone is charging, all other functions work via the Android Auto app without being cable connected. Short of instalkling older AA apk versions I am at a loss. I have tested unit with a iphone and Apple Car Play launches fine so it is not a a HU issue as I assumed. I had used this unit with a P10 Plus and it worked but I had intermittent issue with it as well but with the U11 it has just quit launching all together. I have reset phone to factory and tried fresh, no success. I have enabled Developer mode and enable USB debugging and selected MTP Protocol still no luck.
Anyone experience U11 Android auto issues, super frustrating and dont want to run a custom rom just yet. Suggestions welcome cause I am at wits end beside trying other AA versions from earlier dates or rolling back to Nougat, that I have not yet tried. Phone has worked on Oreo and I got it with Oreo but I was experience intermitent connectivity
Hi all,
Not sure if this is a common problem, but on my Pixel 2 XL, I cannot get any other phone to connect to it via Bluetooth?? I'm trying this so I can try Daydream with the Controller Emulator app but so far, 3 different android phones can pair, but will not connect. Have tried all the basic troubleshooting, any ideas??
Cheers for any help!
S
Same Here
SSanders888 said:
Hi all,
Not sure if this is a common problem, but on my Pixel 2 XL, I cannot get any other phone to connect to it via Bluetooth?? I'm trying this so I can try Daydream with the Controller Emulator app but so far, 3 different android phones can pair, but will not connect. Have tried all the basic troubleshooting, any ideas??
Cheers for any help!
S
Click to expand...
Click to collapse
Yeah, same here. I thought I was doing something wrong so it's kind of nice, sorry, to see I am not the only one having this problem. I had tried all of my phones and even the newest on that I replaced with the Pixel 2 XL. Maybe because we just got an update to 6.1.0? Maybe that's what has changed and I hope we can figure this out. I have a really nice headset that I would like to try Daydream with to see if I want to take the plunge for the Headset and controller.
I was having a similar issue with my Pebble app. Watch would pair with phone, but the app would not connect or would have issues connecting. Turns out I needed to add special permission for unrestricted data usage for the pebble app. Also, bluetooth is by default optimized under battery options. I tried leaving it there and it killed the connection after about 20 minutes and I couldn't reestablish it. So, it's not being optimized now.
I also had issues with phone to phone file transfers using bluetooth. It worked once then stopped. I'm going to see if the file transfer service maybe needs special permissions like the pebble app did.
None of this was an issue on 7.0 so not sure what's changed.
Edit: So the Pebble thing was resolved with a factory reset of the watch. Turns out to be coincidence that it stayed connected for a day after the permissions change. The file transfer over usb is still having issues.
It seems like Google's update did something to it I believe
I know Google dropped Miracast awhile ago, but I really really need it. Chromecast just isn't cutting it. Via build.prop (additions below), I've been able to see the Miracast device but it won't connect. Occasionally I'll even see my homescreen pop up, but it will immediately disconnect. I remember having this problem with an HTC 10 and it had to do with the wifi setting being in battery saver mode. I'm currently unlocked with Magisk on 8.1.0.
Has anyone been successful in getting Miracast to work??
build.prop modifications:
persist.debug.wfd.enable=1
wlan.wfd.hdcp=disable
persist.sys.wfd.virtual=1
I've not heard anyone getting it to work on the Pixel XL 2. Other than I saw this post in the Nitrogen thread here
Just use All Cast. You will need to pay for it, I think it's like $5, but I've been using it for years. Works great and with Chromecast and pretty much anything that allows DLNA. I cast to two TV's, my Nexus Player, XBOX, etc. using it.
gettinwicked said:
Just use All Cast. You will need to pay for it, I think it's like $5, but I've been using it for years. Works great and with Chromecast and pretty much anything that allows DLNA. I cast to two TV's, my Nexus Player, XBOX, etc. using it.
Click to expand...
Click to collapse
Unfortunately I need to it mirror my screen, not just play media. Thanks though!
Hi folk, please I need mirror my Pixel 2 XL on TVs for my job. I've Chromecast ultra but it doesn't work with P2XL (it seems some technical issue made by 8.1.0) in the meanwhile I'm waiting for fix by big G do you know if All cast can do this job?
last_nooby said:
Hi folk, please I need mirror my Pixel 2 XL on TVs for my job. I've Chromecast ultra but it doesn't work with P2XL (it seems some technical issue made by 8.1.0) in the meanwhile I'm waiting for fix by big G do you know if All cast can do this job?
Click to expand...
Click to collapse
This might sound nuts, but is that Chromecast Ultra using a wired network connection? I have no idea the cause but i've had issues with some devices (a samsung tablet for example) connecting to the Chromecast Ultra when it was plugged into the wired connection, often just insta dropping, but it worked flawless when they both were using wireless. Other devices like a Nexus 6p connected perfectly in both network configurations.
Any idea which custom ROMs support Miracast besides Nitrogen OS Oreo? I really need the screen mirroring ability to a windows 10 laptop.
This issue has been logged numerous times on Google Forums - but I wanted to check in with people here. I have the new Note 10+ 5G and having serious issues keeping Android Auto running with my Pioneer Head Unit (please note, I have had NO issues with other Android Phones - OnePlus 7 Pro, Google Pixel 3XL, Sony Xperia 1).
Basically, when connecting the Note 10+, Android Auto worked fine for the first session, then crashed on the second, and since simply won't connect until the phone does a full reboot (then will only work once and run into the same issues). At first I thought DEX was interfering (which it probably is!) but unfortunately there is no way to disable DEX apps or the USB response when plugging in an external connection.
Have others had this issue? Any ideas??
Thanks!
entropylabs said:
This issue has been logged numerous times on Google Forums - but I wanted to check in with people here. I have the new Note 10+ 5G and having serious issues keeping Android Auto running with my Pioneer Head Unit (please note, I have had NO issues with other Android Phones - OnePlus 7 Pro, Google Pixel 3XL, Sony Xperia 1).
Basically, when connecting the Note 10+, Android Auto worked fine for the first session, then crashed on the second, and since simply won't connect until the phone does a full reboot (then will only work once and run into the same issues). At first I thought DEX was interfering (which it probably is!) but unfortunately there is no way to disable DEX apps or the USB response when plugging in an external connection.
Have others had this issue? Any ideas??
Thanks!
Click to expand...
Click to collapse
No issues here in both of my cars
This is not note 10 this is general issues with any not stock google android and android auto. Are you trying to use wireless or usb AA? They just got wireless working with non google devices, but it's very random when it works. I've had the issue you describe(having to reboot) with wireless, USB is far more reliable.
gottahavit said:
This is not note 10 this is general issues with any not stock google android and android auto. Are you trying to use wireless or usb AA? They just got wireless working with non google devices, but it's very random when it works. I've had the issue you describe(having to reboot) with wireless, USB is far more reliable.
Click to expand...
Click to collapse
Thanks so much for your reply. I'm using a direct cable plugged into the Pioneer Head Unit. I have not had this issue with any other handset - and I suspect it may have something to do with DEX. Any other thoughts you may have?
I use it daily on my F150 and I'm not having any issues at all, working perfectly fine. You can try reinstalling the app if you haven't done that already.
Sent from my SM-N975U1 using Tapatalk
Yeah, sorry to hear that. I have a Kenwood DDX9906XR and it does wireless android auto. I have a Google Pixel 3 XL and the Note 10+. I've been able to get wireless android auto working (as well as wired) with NO issues at all. I do think the wireless option is a bit overrated and even sometimes annoying as it doesn't connect as fast as using wired. I just love that Samsung phones are one of the only few left that still use miracast so I get to use the wireless display function in my car.
I have had issue with Waze showing correctly but sometimes when switch to music music plays on screen but not audio. Have to unplu and replug..I did see new apk yesterday so will try it.
My Note 10+(4G model) is having AA issues..
Whenever I plug mine into the Focus RS(SYNC 3) it crashes at 1st use and the Note thinks I am using DEX for PC and to turn it on.
I have tried different cables including Sammy one . and reset the phone to a clean install no joy
I also had an issue with note 10+ connected to my Kenwood Excelon DDX9905S, pandora and spotify - no audio to kenwood would play. I see today there are play store updates for both, perhaps a fix.
on my car, i have to plug in the phone to the car first BEFORE starting the engine. otherwise i get no audio.
netnerd said:
on my car, i have to plug in the phone to the car first BEFORE starting the engine. otherwise i get no audio.
Click to expand...
Click to collapse
aussieak said:
My Note 10+(4G model) is having AA issues..
Whenever I plug mine into the Focus RS(SYNC 3) it crashes at 1st use and the Note thinks I am using DEX for PC and to turn it on.
I have tried different cables including Sammy one . and reset the phone to a clean install no joy
Click to expand...
Click to collapse
entropylabs said:
This issue has been logged numerous times on Google Forums - but I wanted to check in with people here. I have the new Note 10+ 5G and having serious issues keeping Android Auto running with my Pioneer Head Unit (please note, I have had NO issues with other Android Phones - OnePlus 7 Pro, Google Pixel 3XL, Sony Xperia 1).
Basically, when connecting the Note 10+, Android Auto worked fine for the first session, then crashed on the second, and since simply won't connect until the phone does a full reboot (then will only work once and run into the same issues). At first I thought DEX was interfering (which it probably is!) but unfortunately there is no way to disable DEX apps or the USB response when plugging in an external connection.
Have others had this issue? Any ideas??
Thanks!
Click to expand...
Click to collapse
I've experienced many issues with AA with a spectrum of devices. I firsts believed that my vehicle was to blame, due to the technology differences, however I've realized that my Buick Encore Preferred II (ALL STOCK EQUIPMENT IN VEHICLE) immediately broadcasts it's Bluetooth/Wifi-Direct as soon as the head-unit/radio is supplied power. I've concluded that MY issues with android auto came from the app recognizing device movement while I was driving.
Now, I'm no expert, but here's my suggestion.
1. Ensure the USB-C cable supports data-transfer and charging simultaneously. (I've made this mistake by ordering USB-C cables ((that only supported charging....poorly)) )
2. Restore Android Auto's factory settings that came with the phone, ensure any Android Auto data-backups are deleted (for troubleshooting purposes).
3. Install/Update via Play store.
4. Disable bluetooth & "forget" any paired vehicles/head-units on your phone.
5. Remove your phone from your vehicle's bluetooth memory.
At this point, your phone should be plugged in to your COMPATIBLE head-unit***, with neither devices recognizing each other.
6. Start your vehicle's battery/engine & stay stationary.
Your phone may immediately start Android Auto. Some head-units automatically do this for you as a "safety/handsfree" feature.
If Android Auto doesn't automatically initiate when you power your head-unit, run the application.
7. Follow your phone's on-screen prompts to finalize set-up.
8. Ensure your phone is connected to your vehicle's bluetooth.
Worked for me!
Remember, if it's not broken, don't fix it.
*** Supported Cars/Models can be found via google's official website
Same issue here. Worked like a charm with Mate 10 Pro, crashed with my new Note 10 + after a few seconds. Solved it by going through all my USB cables and somehow I found one that worked! (tried 5 different cables). Only a one out of 5 works. My Mate worked with all of them.
Btw: this is the one that worked
Originele Huawei 5A USB Type C Kabel Huawei Mate 20 P20 P30 Pro Type-C Kabel Voor Samsung S9 s8 Plus Oneplus 6 t USB-C Lading Kabel
https://s.click.aliexpress.com/e/kleHUWKk
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
Would like to add that the performance of Google maps is incredibly sluggish when zoomed in. Unusable type of sluggish... Waze is perfectly fine.
works fine for me note 9 and note 10 + 5g in ford kuga. Need to make sure you set your permissions correctly and also go inot dev options and enable unknown sources if using things like spotify etc
If you want to disable dex, i've finally found an app to take the place of Samsung package disabler. . It's called CCSWE. I bought the pro license for $2.99. Samsung package disabler from android police worked great when it worked, but they kept losing your license info and have to re-purchase. Since s10+ i haven't got it to work, says something about failed registration or no license.. something to that effect. Developer is not answering any questions.
I had AA running fine on a Note 8 and an S9. On the Note 10+ it kept disconnecting after a couple of seconds. At the end I have it stable, but I had to modify all battery savings options for this app. I did not disable DeX. When I connect the Note 10 to the head unit (USB), I do get the DeX notification but that does not interfere with the connection anymore.
What I do find annoying is that I have the light and dark mode switched based on day and night time. I noticed that the mode follows the day and night mode of my head unit when connected. However, after disconnecting, the original setting (where it switches based on planned schedule on the phone itself) is no longer activated. I like the detail though, that the phone follows the car scene.
Note 10+ Android Auto on 2017 Ford F150 with SYNC 3 Version 3.0
Android Auto on 2017 Ford F150 with SYNC 3 Version 3.0 worked fine with a Samsung Note 8.
Phone was upgraded to Note 10+ and Android Auto connects and works for a few seconds and then does not work and SYNC 3 reverts back to standard Ford SYNC 3 screen.
Android Auto still works fine with same USB cable and Note 8 in either USB port in truck on SYNC 3.
Note 10+ Android Auto version is 4.5.592854-release
Note 8 Android Auto version is 4.5.592854-release
Note 10+ Android Software is Version 9 Kernel version 4.14.83
Note 8 Android Software is Version 9 Kernel version 4.4.153
Note 10+ Build number PPR1.180610.011.N975USQU1ASH4
Note 8 Build number PPR1.180610.011.N950USQS6DSG4
2017 Ford F150 SYNC 3 Version is Build 18093_PRODUCT Ford Motor Company
I can confirm that in my case I have turned off optimized power and set the phone to maximum performance. I have tried every setting for power and have not had any luck in my case on my Note 10+ phone.
I can confirm that in my case I have run through all of the USB debugging ON/OFF scenarios as well as matching every setting that is on the Note 8 that continues to work with AA and SYNC 3. I have tried every setting and have not had any luck in my case on my Note 10+ phone. I have switched USB cables using everything from Samsung to Anker one-foot to three-foot. All of these cables continue to work with the Note 8 on Android Auto, SYNC 3.
My assumption is this is a new ore revised USB security or access setting embedded somewhere I am unable to locate in the Note 10+ settings/software.
I also tried disabling DEX as that is something new that notifies when connecting USB on the Note 10+ and I figured it might be a conflict with other USB connectivity. No luck there either.
My Note 8 continues to work fine. I am even able to run a Hotspot on the Note 10 + feeding the Note 8 via Wi-Fi connected directly to the USB in the vehicle and that works.
Nothing works on the Note 10+ directly connected to the vehicle via USB with Android Auto and it sounds like it was a problem with the Note 9 and other phones also.
It's frustrating how everything could change so drastically with a new phone release.
I just want Android Auto to work on my new $1100.00 SAMSUNG FLAGSHIP PHONE Note 10+ like it did with my previous SAMSUNG FLAGSHIP PHONE Note 8 ...
Based on all of the previous posts, it appears to be a big problem and I'm sure the others posting have not found resolution, unless they are just not following up with a post.
FYI, Andoid Auto works perfectly on my Note 10 + (and it also worked on my previous Note 8). Using wired set up to 2017 GMC. (And it did work when Dex was on my phone, and it also works now with Dex disabled.)
Thanks
Thanks for responding. Might be a Ford SYNC 3 thing as that appears to be the difference.
tsells said:
FYI, Andoid Auto works perfectly on my Note 10 + (and it also worked on my previous Note 8). Using wired set up to 2017 GMC. (And it did work when Dex was on my phone, and it also works now with Dex disabled.)
Click to expand...
Click to collapse
Frank 8252019 said:
Thanks for responding. Might be a Ford SYNC 3 thing as that appears to be the difference.
Click to expand...
Click to collapse
I believe (I could be wrong) FORD SYNC 3 is Microsoft (back end).
I had no issues on the S10+ so I can't blame One UI . Tried power settings tried to change USB settings (won't let me when connected to the head unit)
Will try power settings next
My AA works with my Chevy Redline no issues