Loading Profile...
Twitter,
Facebook, or email.
A couple days ago I got a notification that there was an update to QuickPull. The notification advised that the new version was 3.5.1 which would now allow a reset even if the device was locked (after 25 minutes). When I went to update, my device indicated that I already had 3.5.1 and overwrote with 3.5.2. I continued with the update. QuickPull works fine if the device is awake or in standby, but seizes the device if it's locked. Upon waking-up the device from the locked state, it asks for my password. After I attempt to enter the password (which it won't let me get past the 1st digit), it advises that I entered the wrong password and creates this cycle that can't be broken unless I manually remove the battery. I'm also noticing that my device indicates that I have 3.5.2 installed, but 3.5.1 is listed as being current in my Mobihand account. What is the current version? QPP is installed on Tour 9630.
UPDATE: Well, I decided to uninstall 3.5.2 and reinstall. Upon doing so, I then learned that 3.5.3 is now the current version. So, I downloaded that and now the device doesn't do that cyclic freezing thing, but it still won't reset when locked. Upon awakening the device while locked, it prompts me for my password, at which time I enter it and the reset process begins without question. It still doesn't work as professed! What's up with this program? How can I get it to work properly?
I’m
frustrated
QuickPull Pro not working & seizing phone
Create a customer community for your own organization
Plans starting at $19/month
-
EMPLOYEE
1Hi there. Sorry about your frustrations. We recently posted another update (v3.5.4) which should resolve the password screen issue and the immediate reboot issue. You can download the update now via Mobihand or from http://tinyurl.com/quickpullpro or http://tinyurl.com/quickpullpro47 for OS 4.7 devices.
Unfortunately, the previous claim that QuickPull would now be able to run while locked or holstered was premature. The RIM operating system prevents any app from performing input simulation while the device is locked or holstered, and this is necessary to accept that final dialog "Reboot Now or Later" which is a system message. We thought we had found a way around this, and in our test lab it appeared to work fine, but all I can say now is it simply does not work in the real world. We are still looking at ways to accomplish this, however. In the meantime, the functionality will behave as it has in previous v3.x series, where a dialog will inform you if a scheduled reset has been missed due to being locked or holstered. -
-
I’m
frustrated
Well... I just tried the newest version and get the same results. Storm w/5.0 - cannot reset the security allow (IT issue BES) - installation says it was successful - when I click RUN, I get the request to grant permissions and I say OK... Then I get "Your device is going into REBOOT in 5 seconds. Press ESCAPE to cancel." It just stays there... NOTHING happens. Same as last time... -
-
I’m
frustrated
I have the same problem, and sometimes my Storm just completely locks up and I have to pull the battery. It really stinks. I wish it would work because it's an awesome idea. This is just too bad. If they can't fix it, I already asked for my money back. -
What I'm looking for is an option that requires no user input. I want the BB to reboot on its own without any user input while it is locked on a set schedule (like the middle of the night). So don't ask me for "Reboot now or later", just do the reboot at the time I scheduled. My BB is usually locked as it is mandated by IT Policy. Thanks.
I have the Tour with OS 5.0.0.484 and QPP v3.6.4. You've indicated that v3.7.2 has addressed the [reset while locked] issue and was available for download on MobiHand. When I check my MobiHand account, all that's available is v3.6.4. Is there another way of accessing v3.7.2 other than AppWorld?
http://faq.steelthorn.com/index.php?V...
Cheers
I followed the link in your previous post and installed v3.7.2 OTA successfully. After installing it, I scheduled QPP to reset at 0500hrs while the device was locked. It worked like a charm! Thanks!