anon(233121)
New member
- Mar 19, 2011
- 1
- 0
- 0
Hi All, Potential fix below
I have been having this issue since I switched from my Nexus 6p to my Moto x4 AndroidOne edition a few months ago. (Samsung Chromebook Pro) and honestly just gave up because I was running in the unstable dev channel for my chromebook anyway.
I switched back to stable last week and was still having this issue (After powerwashing multiple times.) I just got it to work finally, by going to chrome://flags on my chromebook, and enabling a flag that said 'use newblue Bluetooth daemon' just because I was curious. But I did that and it is working now for me.
TL,DNR
I have been having this issue since I switched from my Nexus 6p to my Moto x4 AndroidOne edition a few months ago. (Samsung Chromebook Pro) and honestly just gave up because I was running in the unstable dev channel for my chromebook anyway.
I switched back to stable last week and was still having this issue (After powerwashing multiple times.) I just got it to work finally, by going to chrome://flags on my chromebook, and enabling a flag that said 'use newblue Bluetooth daemon' just because I was curious. But I did that and it is working now for me.
TL,DNR
- Unpair both from each other
- Disable smart lock on chromebook
- Enable smart lock on phone, add trusted place or device (Optional?)
- Turn on flag above
- Reboot chromebook
- Have phone unlocked, turn on smart lock on chromebook, follow steps.
- Profit