How NOT to configure Prey on Android

[raj]

Here's the scenario: In the control panel I set the alarm to ON, the lock to ON with the default password, and set the status to missing. SMS message activated Prey OK, the alarm sounded and the Android phone locked. But my device unlock keypad was set to numeric, and the default password is PREYROCKS or something like that. No way in. So in desperation, having tried everything else I deleted the device from the web site control panel (mistake, I know that now). Under normal circumstances I imagine this is a terminal event for an Andoid device. Fortunately I was saved by a recent IceCreamSandwich upgrade which allows face recognition which I had configured and which finally kicked in (didn't work in low light intensity - why do these things always happen late at night?) and allowed me to re-register the device to my control panel. Once there I reset the unlock code to numeric and resent the SMS message.

I have to say it is FAR TOO EASY to accept the default lock password without realising the consequences if the remote device is set to numeric unlock. There should be unmistakeable warnings on the control panel about this. Although it's suggested in a blog somewhere about changing the default unlock code, nowhere have I seen anything about ensuring the device is able to accept the unlock code before sending it. Of course it's obvious when you're familiar with what the app is doing, but on first installation of an unfamiliar app one mostly just accepts the defaults, and only start changing things when it's installed and working. Seems like I nearly landed myself in a heap of (unrecoverable?) difficulty over this.

[Drew Reece]

I just tested on Android 3.2 on a Galaxy Tab 10.1.

My login was initially set to pattern - Prey locked it & showed the full keyboard when I tapped the password field.
I set the device to use a PIN & relocked it from Prey - it also showed the full keyboard.

Sorry, I don't think the behaviour you describe is normal. The OS should detect that Prey has updated the password type & it should show the correct input method. Perhaps this is an ICS bug? Does rebooting make any difference?
Is your device rooted or using the standard OS?

P.S.
The 'Actions' do cause a lot of pain to new users - even though there is lots of red text warning's people still misunderstand/ don't read/ assume something else. I can't think of any way to improve them without making Prey more difficult to use.

Drew

On 8 Jun 2012, at 13:40, raj wrote:

> Here's the scenario: In the control panel I set the alarm to ON, the lock to ON with the default password, and set the status to missing. SMS message activated Prey OK, the alarm sounded and the Android phone locked. But my device unlock keypad was set to numeric, and the default password is PREYROCKS or something like that. No way in. So in desperation, having tried everything else I deleted the device from the web site control panel (mistake, I know that now). Under normal circumstances I imagine this is a terminal event for an Andoid device. Fortunately I was saved by a recent IceCreamSandwich upgrade which allows face recognition which I had configured and which finally kicked in (didn't work in low light intensity - why do these things always happen late at night?) and allowed me to re-register the device to my control panel. Once there I reset the unlock code to numeric and resent the SMS message.
>
> I have to say it is FAR TOO EASY to accept the default lock password without realising the consequences if the remote device is set to numeric unlock. There should be unmistakeable warnings on the control panel about this. Although it's suggested in a blog somewhere about changing the default unlock code, nowhere have I seen anything about ensuring the device is able to accept the unlock code before sending it. Of course it's obvious when you're familiar with what the app is doing, but on first installation of an unfamiliar app one mostly just accepts the defaults, and only start changing things when it's installed and working. Seems like I nearly landed myself in a heap of (unrecoverable?) difficulty over this.
>

> --
> ------------
> Want to help translating Prey to your language?
> Write us: transl...@preyproject.com
> ------------
> You received this message because you are subscribed to the Google
> Groups "Prey" group.
> To post to this group, send email to prey-s...@googlegroups.com
> To unsubscribe from this group, send email to
> prey-securit...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/prey-security?hl=en_US?hl=en

[raj]

OK, am happy to test it further now I'm more familiar with it. The ICS was an 'internal' upgrade using the software upgrade option from the Galaxy S2 menu, so AFAIK it's the standard ICS 4.0.3 for this device. It didn't detect a change in unlock style (numeric to passphrase in my case). Also, the only red I can see on the control panel page relating to 'actions to perform' is: Important: If you're running Prey version 0.4 or higher, they will run whether it is set as missing or not. That doesn't suggest to me that I'm about to (potentially) harm my device by setting a lock code that it (possibly) won't be able to handle. 

And incidentally, I don't understand how that works for the iPhone (which I am also going to add), which doesn't have an SMS facility. Sorry if I'm being clueles here :)

> prey-security+unsubscribe@googlegroups.com

[Drew Reece]

The iPhone does have SMS (the Messages app), but if your contract or SIM doesn't support it then that part of Prey won't work.
You could still use a Pro account & 'On Demand' mode to send a push notification to an iPhone but it makes Prey less usable, but it can work.

The issue you are seeing may be a bug, you'll need to gather what info you can & hope the developers can test it on the same type of device & OS.

Drew

> > prey-securit...@googlegroups.com

> > For more options, visit this group at
> > http://groups.google.com/group/prey-security?hl=en_US?hl=en
>
>

> --
> ------------
> Want to help translating Prey to your language?
> Write us: transl...@preyproject.com
> ------------
> You received this message because you are subscribed to the Google
> Groups "Prey" group.
> To post to this group, send email to prey-s...@googlegroups.com
> To unsubscribe from this group, send email to

> prey-securit...@googlegroups.com