翠星石 on Nostr: Zergling_man 夜化 nprofile1q…zjeaa >your phone. It's not your phone. ...
Zergling_man (nprofile…pltp) 夜化 (nprofile…3p6r) nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqymejr08suvgx4vxqly8plyyz8899qlm4jw85c73fvzsy84nas5ss4zjeaa (nprofile…jeaa) >your phone.
It's not your phone.
Manufacturers/resellers have the ability to stop the device from charging and therefore stopping it from booting up and even going so far to prevent access to mobile networks;
https://en.wikipedia.org/wiki/Note_7?useskin=monobook#Disabling_of_functionality
>between "connected to wifi" and "connected to wifi (no internet)". The obvious solution is to make some external call and see if it succeeds, but to where?
It just tries to connect to some google server on the internet and sees if the connect() succeeds.
It's really not worth the effort to work out which specific server, so I didn't bother to check.
It's not your phone.
Manufacturers/resellers have the ability to stop the device from charging and therefore stopping it from booting up and even going so far to prevent access to mobile networks;
https://en.wikipedia.org/wiki/Note_7?useskin=monobook#Disabling_of_functionality
>between "connected to wifi" and "connected to wifi (no internet)". The obvious solution is to make some external call and see if it succeeds, but to where?
It just tries to connect to some google server on the internet and sees if the connect() succeeds.
It's really not worth the effort to work out which specific server, so I didn't bother to check.