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 ?
Related
I had a Verizon Pixel XL on which the fingerprint reader failed after the Oreo update. It would just say it could not enroll my fingerprint and to try again, but never worked. A factory reset did not help. So I RMA'd the device and the new one I was sent has Nougat on it. Fingerprint reader is working fine, but now I hesitate to update to Oreo.
So I'm wondering if this is a widespread problem or just something weird that happened to the phone I sent back. Since it's the Verizon Pixel, there's no way for me to downgrade back to Nougat if I have the same problem with Oreo again.
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Click to expand...
Click to collapse
Do you have the Verizon Pixel? I guess my question is: Are there people with the Verizon Pixel who have updated to Oreo and the fingerprint reader is working. Or is it breaking the fingerprint reader on all (or many) of the Verizon Pixels?
cb474 said:
I had a Verizon Pixel XL on which the fingerprint reader failed after the Oreo update. It would just say it could not enroll my fingerprint and to try again, but never worked. A factory reset did not help. So I RMA'd the device and the new one I was sent has Nougat on it. Fingerprint reader is working fine, but now I hesitate to update to Oreo.
So I'm wondering if this is a widespread problem or just something weird that happened to the phone I sent back. Since it's the Verizon Pixel, there's no way for me to downgrade back to Nougat if I have the same problem with Oreo again.
Click to expand...
Click to collapse
I'd say go ahead and update as this does not appear to be a widespread issue. Worst case scenario you can downgrade back to Nougat.
bobby janow said:
Update to Oreo. It'll be fine.
Edit.. although on second thought I might just stick with N. O is not doing that well in the battery life department.
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've actually noticed improved battery life on O compared to N.
mlin said:
I'd say go ahead and update as this does not appear to be a widespread issue. Worst case scenario you can downgrade back to Nougat.
Click to expand...
Click to collapse
How do I downgrade on a Verizon Pixel? Without an unlocked bootloader I thought I don't really have control over those things?
cb474 said:
How do I downgrade on a Verizon Pixel? Without an unlocked bootloader I thought I don't really have control over those things?
Click to expand...
Click to collapse
Sorry, I missed that point. Can only roll back if your bootloader is unlocked. Sorry for the confusion.
mlin said:
Sorry, I missed that point. Can only roll back if your bootloader is unlocked. Sorry for the confusion.
Click to expand...
Click to collapse
Okay. Yeah, that's why I want to be sure about Oreo and the fingerprint reader, before I do the update, because there's no going back on the Verizon Pixel.
cb474 said:
Okay. Yeah, that's why I want to be sure about Oreo and the fingerprint reader, before I do the update, because there's no going back on the Verizon Pixel.
Click to expand...
Click to collapse
The logical answer is that it can't be widespread. If it was then this thread would have hundreds of reports of this happening and the Oreo update would have to be pulled. So a mere Google search even would show a lot of hits. No such thing other than a very few reports. A friend of mine had the same thing happen on his 5x and the solution was to clear the cache in recovery. That was long ago so I'm not sure if that's even still possible but perhaps worth looking into. Nonetheless, I wouldn't worry about it if you want O. Happens again, return it again.
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
thekenster said:
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
Click to expand...
Click to collapse
Did you clear cache in recovery?
Sent from my Pixel using XDA-Developers Legacy app
I have a Verizon pixel XL and I am running official Oreo on my device, however, I have my bootloader unlocked and flashed it manually via adb. I can confirm my fingerprint scanner is working perfectly.
Pixel XL 128GB from Google Store here
Updated via OTA to Oreo, and the fingerprint scanner still works fine to unlock the device.
HOWEVER, it seems to be much more strict when it comes to authentication in Apps such as banking apps, credit monitoring apps, etc. It's annoying because it will temporarily disable the fingerprint login for the entire phone after a small number of failed attempts EVEN if I lock the screen, and unlock with fingerprint in the middle of trying to login to the app with the same finger positioning...
bobby janow said:
The logical answer is that it can't be widespread. If it was then this thread would have hundreds of reports of this happening and the Oreo update would have to be pulled. So a mere Google search even would show a lot of hits. No such thing other than a very few reports. A friend of mine had the same thing happen on his 5x and the solution was to clear the cache in recovery. That was long ago so I'm not sure if that's even still possible but perhaps worth looking into. Nonetheless, I wouldn't worry about it if you want O. Happens again, return it again.
Click to expand...
Click to collapse
Yes I already thought of all that and did all of that. But when you do a search on the Pixel and try to find posts that only have to do with the Verizon Pixel, it's not so simple. Mostly people are talking about the Google Store Pixel or just don't indicate which phone they're talking about. So I posted my question just to double check. I especially wanted to hear that people on the Verizon Pixel XL are not having problems with Oreo and the fingerprint reader, so that I would know that it is working okay in some instances, at least, and can conclude it's not a problem particular to Oreo.
thekenster said:
I recently got the Oreo update on my Google Pixel XL and shortly after my fingerprint reader also stopped working.
It doesn't even recognize the hardware is there, no Pixel Imprint option in security & location menu. Factory reset was no help.
Google is sending me a replacement.
Click to expand...
Click to collapse
That's a little different from the phone that I returned. It recongized the hardware. It just never worked to enroll a fingerprint.
bobby janow said:
Did you clear cache in recovery?
Sent from my Pixel using XDA-Developers Legacy app
Click to expand...
Click to collapse
I don't see an option to clear cache in recovery on the Google Pixel XL. Am I missing something?
thekenster said:
I don't see an option to clear cache in recovery on the Google Pixel XL. Am I missing something?
Click to expand...
Click to collapse
Yes, you're right. It's no longer there I just checked. Sorry about that. Used to be and that did it back then.
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.
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.
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Yes!! I thought maybe it was something I had done myself. I have mine set the same as you, buds, UE Megaboom3, work and home and it asks me about 90% of the time to unlock using fingerprint or pin when connected or at these locations...very frustrating. Used to work flawlessly before Android10. I thought it was because I was using Nova launcher but haven't tested stock launcher.
Sent from my SM-N975U using Tapatalk
ianmb said:
Yes!! I thought maybe it was something I had done myself. I have mine set the same as you, buds, UE Megaboom3, work and home and it asks me about 90% of the time to unlock using fingerprint or pin when connected or at these locations...very frustrating. Used to work flawlessly before Android10. I thought it was because I was using Nova launcher but haven't tested stock launcher.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Great to know! So I am. NOt going crazy!?! Lol... wondering if there will be an update or fix?
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
Great to know! So I am. NOt going crazy!?! Lol... wondering if there will be an update or fix?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
I hope so, I'm tired of having to enter my pin when I'm at home every time I want to use my phone.
Sent from my SM-N975U using Tapatalk
ianmb said:
I hope so, I'm tired of having to enter my pin when I'm at home every time I want to use my phone.
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Seems like alot of the features and the phone got $#@# up with android 10.
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
Seems like alot of the features and the phone got $#@# up with android 10.
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Yeah, some good some bad.
Sent from my SM-N975U using Tapatalk
i have an unlocked phone bought from Australia and smartlock works just fine for me.
i have 3 - 4 devices added as Trusted and i never have to enter the password while connected to them via BT.
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Click to expand...
Click to collapse
I have a N975F Note 10 +,
Android 10 , February security patch.
Stock, no root etc.
Since i had my Note 10 +, from last year, August /October 2019
never had issues with Smart lock.
Presently, i have 8 devices registered with Smart lock.
I had found in general, my Gear S3 watch,
just works perfectly 99 % of time..!
Most of the time I forget that i have a lockscreen.... enabled...!
I have found that on body and location
most of the time have issues.
willcor said:
I have a N975F Note 10 +,
Android 10 , February security patch.
Stock, no root etc.
Since i had my Note 10 +, from last year, August /October 2019
never had issues with Smart lock.
Presently, i have 8 devices registered with Smart lock.
I had found in general, my Gear S3 watch,
just works perfectly 99 % of time..!
Most of the time I forget that i have a lockscreen.... enabled...!
I have found that on body and location
most of the time have issues.
Click to expand...
Click to collapse
What's the difference in models as I have the SM-N975U1 ?
Sent from my SM-N975U1 using Tapatalk
Jiannu said:
What's the difference in models as I have the SM-N975U1 ?
Click to expand...
Click to collapse
The SM-N975F is the international version, Europe etc...
Exynos, 1 x Sim and 1 xsd card. etc
I'm not sure to sure with the SM-N975U1
but i think its......
Snapdragon, Dual sim..?
USA unlock version etc
same here
I have the same issue on sm-n976v i also have noticed that if you have good lock with lockstar activated it also seems to mess with smartlock but i used to turn it off and would start working and now it just doesnt work at all.
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Hej...
Same issue on my phone... I was thinking then is something wrong with mine device but like I see in not only my problem...
Jiannu said:
So I have been having issues with my Note 10+ ever since I've upgraded to Android 10. Did pretty much everything from a reset to a factory reset and delete amd still having issues with smartlock. I have it set to a few devices like my work van, earbuds ,beats and home. I keep getting asked to unlock it when hooked up to any of the devices or at home. Also I've tried to update and delete each one but it still is not working. Even I have ticked when on body.
Wondering if anyone has had same or similar issues with Smartlock?
Sent from my SM-N975U1 using Tapatalk
Click to expand...
Click to collapse
Yep, same exact issue, nothing in smart Lock works for me. Not trusted devices or trusted places. It's just useless. I have resorted to using bixby routines to keep the phone unlocked in trusted places and it seems to work way better than trusted places ever did. But the trusted devices thing is still irritating.
Edit: Just wanted to add this is on numerous Note 10 pluses (always want to try out different. Colors and special editions, lol) and ever since installing the first beta version of Android 10.
chetly968 said:
Yep, same exact issue, nothing in smart Lock works for me. Not trusted devices or trusted places. It's just useless. I have resorted to using bixby routines to keep the phone unlocked in trusted places and it seems to work way better than trusted places ever did. But the trusted devices thing is still irritating.
Edit: Just wanted to add this is on numerous Note 10 pluses (always want to try out different. Colors and special editions, lol) and ever since installing the first beta version of Android 10.
Click to expand...
Click to collapse
Yes I already came to that conclusion shortly after installing Android 10 official. Hopefully there will be a patch or fix soon
Sent from my SM-N975U1 using Tapatalk
Mine is fine when connected to my TicWatch or JBL headphones but NEVER works with location-based SmartLock. Never has, even on Android 9. Set address and GPS location, nothing works for location for me but never an issue with BT connected devices.
elogikal said:
Mine is fine when connected to my TicWatch or JBL headphones but NEVER works with location-based SmartLock. Never has, even on Android 9. Set address and GPS location, nothing works for location for me but never an issue with BT connected devices.
Click to expand...
Click to collapse
On Android 9 smart Lock worked better than it did on any of my pixel phones which was refreshing. Location and device both worked flawlessly. But not any more unfortunately.
Got my 6 Pro yesterday, and after trying to log into the Starbucks app, the only error I get is "A system error has occurred. Please try again later" I can even type in random characters and numbers into the username and password field too, and still results in the same error. App version 6.13.1 Tried on cellular (Verizon) and wi-fi. Uninstalled, reinstalled, etc. Opened a ticket with Starbucks. Is anyone else experiencing this issue?
t3hbutt3rs said:
Got my 6 Pro yesterday, and after trying to log into the Starbucks app, the only error I get is "A system error has occurred. Please try again later" I can even type in random characters and numbers into the username and password field too, and still results in the same error. App version 6.13.1 Tried on cellular (Verizon) and wi-fi. Uninstalled, reinstalled, etc. Opened a ticket with Starbucks. Is anyone else experiencing this issue?
Click to expand...
Click to collapse
I had the same issue. Just thought starbucks was having a problem. Apparently not. Just tried it again and can't log in. Via T-Mobile and Wifi as well.
t3hbutt3rs said:
Got my 6 Pro yesterday, and after trying to log into the Starbucks app, the only error I get is "A system error has occurred. Please try again later" I can even type in random characters and numbers into the username and password field too, and still results in the same error. App version 6.13.1 Tried on cellular (Verizon) and wi-fi. Uninstalled, reinstalled, etc. Opened a ticket with Starbucks. Is anyone else experiencing this issue?
Click to expand...
Click to collapse
So if you log into the mobile web site, go to menu - account - card management, you can pay from there or add money to your card.
It's a workaround anyway. You can also install the PWA app from the chrome menu at that point as well. That will create an icon in your launcher which will open up to the right page/screen to pay from.
Is it working on other phones with Android 12? I would bet they have an issue with that.
Same issue here. I also used the mobile web to workaround this morning.
TonikJDK said:
Is it working on other phones with Android 12? I would bet they have an issue with that.
Click to expand...
Click to collapse
Yeah, maybe they just haven't updated their app for Android 12. Doesn't sound like a specific Pixel 6/Pro problem, but who knows...
UK version 7.3.1 working ok on the Pro. No login issues etc seen.
Not working on my 6 Pro either. I don't think it's an issue with android 12, the app works fine on my pixel 4xl on Android 12. Maybe it has to do with tensor?
<insert comment here about supporting your local coffee shops>
all jokes aside sounds like an Android 12 issue, reach out to the developer email from the Play Store page and also I have found leaving a review on the Play Store explaining the issue sometimes gets some attention to the issue as well.
plasticarmyman said:
<insert comment here about supporting your local coffee shops>
all jokes aside sounds like an Android 12 issue, reach out to the developer email from the Play Store page and also I have found leaving a review on the Play Store explaining the issue sometimes gets some attention to the issue as well.
Click to expand...
Click to collapse
I don't thinks it's an Android 12 thing. The app works perfectly normally on my Pixel 4XL, and that's on Android 12. The app never stopped working even when that phone was first added to the Android 12 beta. It seems like a specific pixel 6 problem to me
It's not an Android 12 thing. Wells Fargo is having the same problem. My Pixel 5 can log into both apps. Apparently there's something going on with the 6.
solarus2011 said:
It's not an Android 12 thing. Wells Fargo is having the same problem. My Pixel 5 can log into both apps. Apparently there's something going on with the 6.
Click to expand...
Click to collapse
I bet it has to do with the security stuff on tensor
I have the same problem, I cannot log in on my Pixel 3 and Pixel 6 Pro, Pixel 5 is working fine. I logged out and log in again on my Pixel 5 but not on the other Pixels. Pixel 5 and 6 Pro have Android 12 installed and Pixel 3 Android 11
I had the same problem all day yesterday but I was able to login this morning.
The difference between today and yesterday is that now I have Magisk rooted whereas yesterday it was just unlocked bootloader. I'm not sure if that was the cause.
Cares said:
I had the same problem all day yesterday but I was able to login this morning.
The difference between today and yesterday is that now I have Magisk rooted whereas yesterday it was just unlocked bootloader. I'm not sure if that was the cause.
Click to expand...
Click to collapse
I don't think the issue has to do with the bootloader because mine is locked on my 6 Pro and 4XL. App works on the 4xl but not the 6 pro. The app is working for you on pixel 6?
Josh.haveman1 said:
I don't think the issue has to do with the bootloader because mine is locked on my 6 Pro and 4XL. App works on the 4xl but not the 6 pro. The app is working for you on pixel 6?
Click to expand...
Click to collapse
Yes it wasn't work all day yesterday until I was forced to wipe my phone so that I could root. Now I can log in.
Cares said:
Yes it wasn't work all day yesterday until I was forced to wipe my phone so that I could root. Now I can log in.
Click to expand...
Click to collapse
Ohh. Weird. I wonder what changed.
I was just able to log in. The Starbucks app didn't update, but there was a system update for the phone earlier. Decided to try and login for fun and it worked. Hopefully it's working for everyone now. Thanks for your assistance to all who helped. Cheers!
I had the same problem originally. I forgot about it until I started reading this thread. I just tried it now when it worked for me perfectly fine. Maybe the update that came out fixed whatever was causing that.
It's working for me now as well!