QuickPull Beta2 for OS 5.0

Edit Subject

So far this is looking good. I was able to install and then perform a reset. I was never able to perform a reset with the last version. I'll keep testing and reply back with any issues I find.

FYI I am on a BES with an official non-leaked version of 5.0.

The instructions you listed weren't quite right. After Step four the phone required a reset. When the phone came back up there was an error message of some type regarding Quick Pull, something about "cross communication." I moved on to Step 5, no problem, permission with Security Timer still grayed out. Once the phone came back up after the battery pull in Step 6, I opened the program and it asked me to view permissions again, I just checked to make sure everything was okay (the one permission was still grayed out and set to deny and I can't change it to allow) and then saved. I hit reset and it worked. After the reset when I opened the program it asked me to view permissions again. Hope this helps.

IT worked for me - not sure of the steps I followed - but it was pretty "automatic" Storm asked me to give trusted status, said ok; I did delete the old version. When I tried to run the beta, asked me for a code, used the old one and it worked; tried the reboot and it worked fine.

ok im using 5.0.0.348 (8900) and the previous qp pro and betas didnt work so i tried the new beta 2 and set permissions to deny, then allow did battery pull set the app timer and quess what ?> IT FINALLY WORKED so qp pro is a go on beta 2 os v5
thx

I installed the beta 2 on my storm 2 to help solve the problem with the scheduled reset issue I was having with the original beta. The initial "scheduled" reset went well (this wasn't really a problem for me with the original beta). I'll check tomorrow to see if it resets at 2:50pm or not and let you guys know.

Installed beta 2 on my Bold, which is using OS 5 .314. After going through the permission fix I'm pleased to say Quick Pull is working like a champ. Thanks.

Strong work,
I am a BES user and my company will not change the security timer lock out. I downloaded beta 2 last night and was able to perform a manual reset without difficulty. I have not had an opportunity to check the scheduled reset as of yet, but I am very encouraged that it will work just as advertised. Installation was a breeze on my Storm with OS 5.0.0.328. It did not require any convoluted steps to get the software to work. I accepted the requests for permission for the software and it worked like a charm. I will be purchasing the pro version shortly so as to eliminate the advertising screens.

The beta 2 fixed the scheduled reset problem I was having with the original beta on my storm 2. It ran as scheduled yesterday. Thanks!

No problems installing beta 2. beta 1 worked to reset device but the scheduling feature only worked once. Here's hoping. The only difficulty I am having is the touch screen buttons are harder to navigate. Before OS5 the keyboard would go away and I could see the whole navigation screen and I can't click right on the button I want to, I have to scroll through all of the buttons to get to the one I want. It seems to function better than beta 1 did. Thank you.

Hi! I am on VZW official 5.0.0.328 and am on BES. I cannot allow the "Security Timer Reset" permission, so that component ("Interactions") always remains as "Custom" (with "Deny" set on this parameter). In accordance with the instructions, I set all to "Deny" and then attempted to reset all to "Allow", but this particular setting would not change. It must be that my IT Policy forbids this setting. The result is that, when locked with a device password (which I use), the device cannot reboot on schedule. If it happens to be unlocked at the time that the schedule is set for, it reboots just fine...but not when locked (which it would be if I, for instance, set it to reboot every night at 0200hrs while I am asleep). Cheers!

I tried both links for the beta2 and both links are broken.

I'm on a run-of-the-mill BES 4.1.6 server. Beta 2 seems to works fine on my 9530 (I can't remember an error recently, but I know the scheduled reboots were a little hit-or-miss during Beta 1). I *do* seem to have a problem with having to manually turn the wireless network off, then on again in order to get connected, as I wake up to find my phone unable to see any network.

The only other thing is a prompt when I enter QuickPull Pro: QuickPull is requesting changes to its application control permissions.

It then prompts me to change Interactions and Security Timer Reset.

Of course, I'm not actually able to change those permissions, but it doesn't seem to affect the actual operation of QuickPull. I'm not sure if those permissions have anything at all to do with the wireless network not being seen after a scheduled reboot.