![]() If anything, I think the opposite seems more reasonable to assume given no actual evidence. Why do you assume this? This seems like a huge oversight in the design of ADM, so I don't see why it makes sense to assume this is true without proof. Your assumption is that the remote wipe no longer works if the account password has been changed.In the event my phone is stolen/lost, I'd probably change my Google password (.) will the remote wipe still work since the Google password changed? And if I was to login on another computer using my real password, the verification code gets sent to my dumbphone which I check and use.Īndroid Device Manager makes it easy to locate, ring, or wipe your device from the web. I still have my laptop as my authorized login, that is, I can use my real password on the laptop, everywhere else Google is accessed, is using the random generated password. That is what I was referring to, in my case, I have the application called "My smartphone google account signin", and if it gets lost, I click Revoke, even after factory reset, data is wiped cleanly for my peace of mind. In event of phone or should I say, device getting lost/stolen, its a matter of simply clicking on it. See the Revoke beside each application specific password. To clarify: Your account on the device is called a Application specific password. I use a spare, crappy phone that I carry with me everywhere, zero chance of anyone trying to steal it, that receives the Google SMS notification, and yes, its a dumbphone :) Edit ![]() ![]() That is what I use here, where-ever I log in, I get an SMS direct to me, asking to enter the verification code, no one else has it.Īlso, it would be easier to just revoke it from your Google Account settings page, i.e. Why not for sake of it, activate 2-step authentication on your Google account?Īnd just use the random generated password instead, be sure you have enabled Google to SMS you for any login attempts on your Google account, and keep your real password hidden.
0 Comments
Leave a Reply. |