Open ferencbrachmann opened 7 years ago
I haven't tested a OnePlus3 so I can't comment directly. The only reason I can guess this is happening is if the BLE stack isn't good (the OnePlus1 had this issue) If that were the case, there would be only partial scanning and that wouldn't trip the initial alert.
The surefire test of this theory is to set a beacon to broadcast fairly rapidly (say 300ms) and the run nRF Connect and collect scan dataon that beacon for 15 seconds. If you see a large number of missing adv packets, there's your problem.
I'm so sorry, I clearly misread this issue. No that is not normal. You should never be forced to manually turn it on. I'm not sure what would trigger that.
@scottjenson a client of ours noticed that on the OnePlus3 you need to turn on "Nearby links available" and "Devices ready to set up" manually. Is this the normal intended method? What we've learnt from most Android installations that the onboarding to Nearby is completely seamless.