Good morning,
Has anyone else had issues with setting up Android Pay on their watch with the 2XL? I have an LG Watch Sport that worked great with my Nexus 6P, but when I try to set it up on with my Pixel 2 XL, it tells me it cannot be set up because it's rooted, has an unlocked bootloader, or a custom ROM. Both are stock, but both are on the Beta Program, but I didn't have that issue when the Nexus was on beta. I've tried resetting the watch with no luck. Any ideas?
Thanks!
ferdeenand said:
Good morning,
Has anyone else had issues with setting up Android Pay on their watch with the 2XL? I have an LG Watch Sport that worked great with my Nexus 6P, but when I try to set it up on with my Pixel 2 XL, it tells me it cannot be set up because it's rooted, has an unlocked bootloader, or a custom ROM. Both are stock, but both are on the Beta Program, but I didn't have that issue when the Nexus was on beta. I've tried resetting the watch with no luck. Any ideas?
Thanks!
Click to expand...
Click to collapse
it doesn't work in my country so i can't test
BUT root brake android pay from 2016 i believe
you have to use the hide function in magisk
hide alllllllll the apps that don't need root
then reboot then clear data from android pay/google service/ play store
then try again
After digging around online through the Android Beta Google+ page, it seems that it doesn't work on the Wear beta, but since it was already active with the 6P, it continued to be active. Pairing with the Pixel reset the watch and that's what stops it from working. I'm leaving the beta and will downgrade the OS when I get home to a charger.
Related
I've tried resetting it, deleting the wear app, unpairing bluetooth...even tried it on my tablet and the thing just will not find the update. My friend did it the other day on his new phone and it grabbed the new update straight away.
I tried contacting Motorola support and they were useless... Does anyone have any other suggestions? I wouldn't be that bothered but I feel the wifi would make me use the watch far more, plus with the latest version it works with iPhones and I'm thinking of switching to an iPhone 6S Plus!
Thanks in advance for any help.
Synthesthesia said:
I've tried resetting it, deleting the wear app, unpairing bluetooth...even tried it on my tablet and the thing just will not find the update. My friend did it the other day on his new phone and it grabbed the new update straight away.
I tried contacting Motorola support and they were useless... Does anyone have any other suggestions? I wouldn't be that bothered but I feel the wifi would make me use the watch far more, plus with the latest version it works with iPhones and I'm thinking of switching to an iPhone 6S Plus!
Thanks in advance for any help.
Click to expand...
Click to collapse
I would suggest using an older version of Android Wear. I used version 1.3.0.2139573. Once I did this I could update my Moto 360 from 4.4w2 to 5.1.1 without a problem. After that I had to update the Android Wear app on my phone to the latest build and it's all working flawlessly so far :good:
Does anyone here have a chromebook they use with their Oneplus 3?
I got a chromebook recently and can't pair the OP3 to the chromebook, and as a result can't use Smart Lock to unlock the chromebook by unlocking the phone. Am I doing something wrong or is the chromebook or the phone the issue?
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Anova's Origin said:
I have an Acer Chromebook 14 and smart unlock works as expected. Is Bluetooth on for both your chromebook and OP3?
Click to expand...
Click to collapse
Are you on stock OOS?
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
peterk-1 said:
I can set my car and PC BT as trusted devices in Smart Lock. BUT not Nexus 7 & 9 and Pixel C tablets!! - neither can I set any of them as trusted devices with each other. There are inconclusive "internet" threads about it. I think it may be Google being "economical with the truth" and hoping this issue will go away in time.
Click to expand...
Click to collapse
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
2x4 said:
that's interesting, but I'm referring to unlocking the chromebook, using my oneplus 3 as the "trusted device" so to speak.
my OP3 also works fine to unlock itself using my car's BT as trusted device.
Click to expand...
Click to collapse
Sorry - I missed the point in my explanation. I should have made clear the "trusting" doesn't work in either direction. In the case of attempting to set up any device to unlock a Pixel C, the Pixel C menu Smart Lock > Trusted devices doesn't open to BT / NFC options but instead gives an "error" message " Trusted devices feature is not available to use". This has been the case with Android M and N so it has been suggested that this is a hardware restriction. The relevance? - Pixel C started life designed as a Chrome device. Another suggestion is that there is a coding error and GPS has been included as a requirement - I doubt this since trusted locations works.
2x4 said:
Are you on stock OOS?
Click to expand...
Click to collapse
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Anova's Origin said:
Yes, stock OOS 4.1.0, rooted with Magisk and on Franco's r14.
Is Bluetooth on for both your phone and chromebook? Maybe try re-pairing them.
Click to expand...
Click to collapse
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
2x4 said:
i'm on the freedom OS OB with magisk and stock kernel. is it my chromebook that's having the issue perhaps? I've tried unpairing and re-pairing on both, the chromebook says it can't connect to my phone
Click to expand...
Click to collapse
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Anova's Origin said:
Is your chromebook up to date in terms of Chrome OS updates? If you could pair them before but not now, maybe try powerwashing your chromebook.
Click to expand...
Click to collapse
yes it is up to date
2x4 said:
i only got it a few days ago, it's the samsung chromebook plus. It paired before but smart lock never worked once, even when i hit the try now button after setting it up. I've jumped on the beta channel since then and still not able to get it to work.
Click to expand...
Click to collapse
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
MrWilsonxD said:
I had this exact issue with my chromebook plus and my oneplus 3 while on oos. It worked fine up until maybe two or three weeks ago on oos.
It started working for me when I un greenified the Google app. It could be also I switched to resurrection remix.not sure which fixed the issue >__<
Cool to know somebody else is rocking the oneplus 3 and the chromebook plus!
Click to expand...
Click to collapse
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
2x4 said:
Thanks for the input! I just wanted to make sure it wasn't the Samsung Chromebook Plus. Hopefully it gets fixed with the OnePlus 3 at some point
Click to expand...
Click to collapse
My pleasure. I doubt it's a problem with the CBP. Probably something to do with oxygen OS unfortunately.
added a new user to the chromebook today, and enabled smartlock with her phone (Nexus 6P) with zero issues - it's definitely the Oneplus 3.
i'm current on freedomOS community beta version. not sure what the issue is...
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
F4uzan said:
I had the exact same issue weeks ago, I'm unsure what the fix was because I had a whole lot going in between finding the fix for it, I powerwashed the Chromebook and reinstalled the ROM I used (with a clean wipe, of course). It's either of those that fixed it for me.
Click to expand...
Click to collapse
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
2x4 said:
im doing a clean flash now - what ROM are/were you on if you don't mind me asking?
and when you clean flashed, did you use Google's "restore a backup" during setup?
Click to expand...
Click to collapse
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
F4uzan said:
For the ROM, it's a custom-built AOSP ROM, but I also jumped to LineageOS 14.1 for a short while (and it also works there as well)
No, I use the other option that don't require me to restore things.
Click to expand...
Click to collapse
tried a clean flash of the ROM I'm currently on (FreedomOS based on OOS beta), and the issue still persists.
I'd be open to using another ROM but haven't ever had a reason to switch and I like the optimal camera performance with OOS
just tried a clean flash of lineage OS (https://forum.xda-developers.com/oneplus-3/development/rom-t3532088) - smart lock STILL didn't work (I keep getting the "can't find your phone" error message)
what specific ROM(s) did you see it work on @F4uzan ?
Just got the 2 XL and ported over to T-Mobile to get the rebate, and one issue so far...
I can pair (says successful) with my car (2007 BMW X5) but it will not connect. It just tries over and over, no error messages, but no connection. Deleted on both side and tried again three times, same result.
Got home and paired with a headset.
Anyone else have issues with car pairing (or more precisely with it connecting afterwards)?
I've never had a phone which did not pair with that car (been through maybe 6 with wife's and mine). Any suggestions how to tell why it will not pair?
Phone is on vanilla 8.0 as updated today without root or unlock so far.
Linwood.Ferguson said:
Just got the 2 XL and ported over to T-Mobile to get the rebate, and one issue so far...
I can pair (says successful) with my car (2007 BMW X5) but it will not connect. It just tries over and over, no error messages, but no connection. Deleted on both side and tried again three times, same result.
Got home and paired with a headset.
Anyone else have issues with car pairing (or more precisely with it connecting afterwards)?
I've never had a phone which did not pair with that car (been through maybe 6 with wife's and mine). Any suggestions how to tell why it will not pair?
Phone is on vanilla 8.0 as updated today without root or unlock so far.
Click to expand...
Click to collapse
I have similar issues, and had them with my 6p. With that phone, they were resolved by the October security update. Hopefully the same thing will happen on the Pixel 2 XL, but when the October update will come is anyone's guess.
It's worth noting I also have a BMW. Sometimes switching to another device and back corrects the issue for me.
Sent from my Pixel 2 XL using Tapatalk
My bluetooth works with my wife's chevy traverse just fine. I am able to stream music and use the phone.
Pixel 2 XL and 6P Owner here. The Pixel 2 XL connects to my 2014 328i but does not stream music from Spotify. It connects every once in a while but when it does, I'm not able to control it from the Steering and the metadata is all wrong. I have already sent a bug report to Google Support.
My 6P is running August Nougat 7.1.2 and it works perfectly with the BMW. I'm assuming this is just an Oreo issue and will be fixed hopefully with the November security patch.
So it sounds like it is not a hardware issue with my phone then, if it's prevalent (and reminiscent of the prior pixel, sadly). When my wife gets back need to try the Sequoia, but it's the X5 I drive all the time.
Worked in the Sequoia, tried BMW again, pairs successful (at least the BMW says it did) but won't connect, just continual retries. Maybe it just doesn't like German cars -- can I explain the X5 was made in South Carolina?!?
Linwood.Ferguson said:
Worked in the Sequoia, tried BMW again, pairs successful (at least the BMW says it did) but won't connect, just continual retries. Maybe it just doesn't like German cars -- can I explain the X5 was made in South Carolina?!?
Click to expand...
Click to collapse
Try turning off Contacts and Text Messages in the Bluetooth profile. This worked with my 3 series, but not so well with my wife's X3. My phone actually makes her iPhone not work in her car as long as those two features are enabled on my phone.
Sent from my Pixel 2 XL using Tapatalk
@amaddux thanks, had already tried that (only showed contacts not text). No joy.
I assume there's no point in contacting google support?
Linwood.Ferguson said:
@amaddux thanks, had already tried that (only showed contacts not text). No joy.
I assume there's no point in contacting google support?
Click to expand...
Click to collapse
There is a thread on the issue with the Nexus 6p on Google's forums. It ends with Google talking about the October Security update fixing it, with more fixes to come.
Here is the thread https://support.google.com/pixelphone/forum/AAAAb4-OgUsiJeDphsoOJ4
Sent from my Pixel 2 XL using Tapatalk
I have an 07 328i. It pairs, but never connects. Works fine with my 14 Silverado. Hopefully, a security patch knocks this out.
Sent from my Pixel 2 XL using XDA-Developers Legacy app
My pixel 2 xl won't connect to my aftermarket kenwood DDX492 receiver. The error says invalid pin or passkey. However the displayed pin is the same on both devices.
I signed up for the beta program last evening, the 8.1 beta was available immediately, I installed it and this morning took a drive -- works fine now, did not even have to re-pair to get phone (I had contacts off, did repair with contacts on and they came back also).
So 8.1 definitely has some fixes in there for bluetooth.
Same issue here with m135i from 2012.... My pixel 2 XL paired successfully but cannot download contacts not other data from the phone. It even makes crash my USB key and stop music from it after a few seconds. Does the beta 8.1 is stable enough for a daily?
thayil said:
Same issue here with m135i from 2012.... My pixel 2 XL paired successfully but cannot download contacts not other data from the phone. It even makes crash my USB key and stop music from it after a few seconds. Does the beta 8.1 is stable enough for a daily?
Click to expand...
Click to collapse
I am not a heavy phone feature user, but so far no issues. Voice, car phone, text, email (lots), general news apps - all worked same before and after.
Linwood.Ferguson said:
I am not a heavy phone feature user, but so far no issues. Voice, car phone, text, email (lots), general news apps - all worked same before and after.
Click to expand...
Click to collapse
I've had problems with video apps not liking the DP released in the past. Things like Hulu, At Bat, etc... Do you use any of those types of apps?
Sent from my Pixel 2 XL using Tapatalk
Just tried HBO Go and Youtube without issues.
Note I didn't install the DP from files, but through the OTA from the beta program (not sure that matters, but FWIW).
I've been having issues with my wireless earbuds. They work just fine with other phones, but with the Pixel 2XL the audio keeps going in and out on the right earbud. Super annoying.
What i've played around with this past couple days on my bluetooth with my '17 F350 is in the BT settings you can toggle "phone, media, contacts" and I just wanted media and phone wouldnt connect. Now I toggled on Phone and it'll connect a lot better than it use to. No idea why that has to be on to get it to work though
Moostafa29 said:
I've been having issues with my wireless earbuds. They work just fine with other phones, but with the Pixel 2XL the audio keeps going in and out on the right earbud. Super annoying.
Click to expand...
Click to collapse
Gilley said:
What i've played around with this past couple days on my bluetooth with my '17 F350 is in the BT settings you can toggle "phone, media, contacts" and I just wanted media and phone wouldnt connect. Now I toggled on Phone and it'll connect a lot better than it use to. No idea why that has to be on to get it to work though
Click to expand...
Click to collapse
Sounds like we are getting several P2 and P2XL bluetooth updates and fixes in the November security patch. I would sit tight as I'd imagine this will fix most, if not all of these issues.
https://www.androidcentral.com/pixe...tw_card&utm_content=63809&utm_campaign=social
---------- Post added at 05:15 PM ---------- Previous post was at 04:44 PM ----------
mrmaddog said:
My pixel 2 xl won't connect to my aftermarket kenwood DDX492 receiver. The error says invalid pin or passkey. However the displayed pin is the same on both devices.
Click to expand...
Click to collapse
Linwood.Ferguson said:
I signed up for the beta program last evening, the 8.1 beta was available immediately, I installed it and this morning took a drive -- works fine now, did not even have to re-pair to get phone (I had contacts off, did repair with contacts on and they came back also).
So 8.1 definitely has some fixes in there for bluetooth.
Click to expand...
Click to collapse
Linwood.Ferguson said:
I am not a heavy phone feature user, but so far no issues. Voice, car phone, text, email (lots), general news apps - all worked same before and after.
Click to expand...
Click to collapse
amaddux said:
I've had problems with video apps not liking the DP released in the past. Things like Hulu, At Bat, etc... Do you use any of those types of apps?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Linwood.Ferguson said:
Just tried HBO Go and Youtube without issues.
Note I didn't install the DP from files, but through the OTA from the beta program (not sure that matters, but FWIW).
Click to expand...
Click to collapse
Moostafa29 said:
I've been having issues with my wireless earbuds. They work just fine with other phones, but with the Pixel 2XL the audio keeps going in and out on the right earbud. Super annoying.
Click to expand...
Click to collapse
Gilley said:
What i've played around with this past couple days on my bluetooth with my '17 F350 is in the BT settings you can toggle "phone, media, contacts" and I just wanted media and phone wouldnt connect. Now I toggled on Phone and it'll connect a lot better than it use to. No idea why that has to be on to get it to work though
Click to expand...
Click to collapse
Hi all,
Just downloaded the November release and can confirm that Fast Pair works now and BT is fully functional. I forgot the device on my car and on my phone upon reboot after installing the update. Turned my car on, turned BT on and it really paired and connected within seconds. Tested with 3 more speakers and even went back to car to test again. All good to go. There were a ton of patches listed for BT specific to P2 and P2XL, glad they fixed this so quickly.
Same for me. But I had to update connecteddrive on my BMW M135i though. Finally I don't know if the November patch did something or it was the car's update... FYI.
I've been looking for an answer for this for a while but couldn't find anything, not even Samsung was of any help, as they said the active 2 watch doesn't work well with pixel 3, even though online o saw multiple people using it without issues.
So the thing is I've owned a gear S3 for 2 years, working great from Pixel 2 XL to 3 XL. I just bought a newer version of The watch, the active 2. The app couldn't find it, so I tried uninstalling it, and finding out I couldn't install it again. I keep getting an error message from Google play saying the app couldn't be installed. I tried downloading the apk for the app, but also got a "app not installed" message. Now I can't use the watch. I can still install the old apk, that doesn't find the watch. But can't get a later version because nothing will install. I can't even install the active 2 plugin, either through the app store or from an apk. Not sure what else to do. I really like the watch and didn't want to go back using my old one
I have the same watch, with pixel 3 xl, everything works as expected here..
@DeskPixel what rom are you using? I noticed that kind of thing happen when I was using custom roms, but everything was fine on the official rom.
I'm currently running Havoc and have not come across any issues with my Active2
As per the thread title, has anyone successfully gotten any of the streaming apps to work on Android Auto that has root? I was thinking that I would be able to get it working once I had root but that's not the case. I can get them working on my Galaxy or LG devices (both unrooted) just fine but not on my pixel which has root
Android 12 and recent AA versions seem to break screen mirroring apps. Haven't tried CarStream or similar.
LLStarks said:
Android 12 and recent AA versions seem to break screen mirroring apps. Haven't tried CarStream or similar.
Click to expand...
Click to collapse
I haven't been able to get anything working including car stream, fermata, car tube. Absolutely nothing is working. I was hoping someone here has figured out the trick with having root to make it happen
Negan said:
As per the thread title, has anyone successfully gotten any of the streaming apps to work on Android Auto that has root? I was thinking that I would be able to get it working once I had root but that's not the case. I can get them working on my Galaxy or LG devices (both unrooted) just fine but not on my pixel which has root
Click to expand...
Click to collapse
Did you properly set up Zygisk (-> Enforce Denylist)? And set up Universal SafetyNet Fix?
I do not use Androidauto, but all the apps I'm using (banking, security, google pay etc) work without a problem once Zygisk is properly set up.
Yes but it's not likely a safety net thing though
The stream2auto and AA Tweaker threads have some clues. But I've not tried them myself.
I've been able to recently get stream2auto working for one day by uninstalling AA and installing version 6.9.613744. Lost it next time I tried to use it. Also needed to clear app data for AA and Google Play services. This is due to a combination of AA and Google Play Services doing their best to remove third party apps from AA.
I've seen some suggestions for using LuckyPatcher to rename screen2auto. Also seen some for detaching AA from the playstore, but have not tried those for a more permanent. Read through the links posts/threads for more insight.
https://forum.xda-developers.com/t/...te-android-auto-utility.4194239/post-86087981
https://forum.xda-developers.com/t/...g-only-for-root-devices.4062787/post-84806229
Screen2Auto and AAStream suddenly started working for me. You still have to install with AAEase or AAAD.
Android Auto 7.3.120444
LLStarks said:
Screen2Auto and AAStream suddenly started working for me. You still have to install with AAEase or AAAD.
Android Auto 7.3.120444
Click to expand...
Click to collapse
Lucky you. I was able to get those to install and both show up in AA but fc when trying to launch. AA 7.1.614574. will try updating to that version and see but I'm not optimistic.
Interestingly enough yesterday when I started AA I got that warning that happens every so often where AA doesn't start and makes you have to stop and agree to the terms again and everything started working again. Idk if it's just luck or there's something to it but what I did was used AAAd to download catstream 2.05 and the AA Aio tweaker app to patch catstream and it works... For now