Been a while since I've posted here, but I come bearing beta versions! We need more testers for our latest version of QuickPull for OS 5.0+. We are working on a version that is easy(er) to use and also lighter and faster. This version also addresses some issues when running on new OS 5.0 builds (eg. 454+). Check out more here:
At first it did not work on Bold 9000 OS 5.0.610., so I deleted it.
After seeing comment below from PKCable, I redownloaded QuickPull beta, set it up, and then did a battery pull and now this beta certainly does work!!!!!
Not working on my 9550 on 607 either, least not YET, gonna try a traditional pull and see if that helps it along. Also I wonder if I can use my reg code from my full version of 3.0? I'm gonna try anyways.
EDIT: You can disregard my response here as I will use your forum for bug reporting as instructed. Already duplicated (for the most part) this post on your forum.
EDIT2: FTR It's working here too, since the real pull.
Installed over latest official/registered version of QuickPull and it worked like a charm. I'm running VZW official 5.0.0.591 OS (with latest official VZW update/patch as well) on my Tour 9630.
Works fine. Haven’t' tested the Monitor option. I was wondering why we would need a restart once the memory researches a certain MB - frees up memory? But by how much? I would think a shut down would be feasible.
So if I set it to restart when the Mem reaches 5MB, it restarts then... I will have more then 5MB once it reboots? But by how much? Then when it reaches 5MB again it restarts? In a loop?
Works fine. Haven�t' tested the Monitor option. I was wondering why we would need a restart once the memory researches a certain MB - frees up memory? But by how much? I would think a shut down would be feasible.
So if I set it to restart when the Mem reaches 5MB, it restarts then... I will have more then 5MB once it reboots? But by how much? Then when it reaches 5MB again it restarts? In a loop?
The memory leaks or drops (or whatever some want to call it) on Blackberrys are inherent to the device. And some devices (like Bold 9000) have less available memory to begin with. If you leave apps open (intentionally or not), you will use memory. Some third party apps and especially themes do cause leaks. A battery pull will free up memory, so a scheduled daily "pull" with QuickPull or one when your memory is at a certain level will get your memory back up. I schedule a re-boot with QuickPull every morning at 2:00 AM and the device runs fine all day.
The memory leaks or drops (or whatever some want to call it) on Blackberrys are inherent to the device. And some devices (like Bold 9000) have less available memory to begin with. If you leave apps open (intentionally or not), you will use memory. Some third party apps and especially themes do cause leaks. A battery pull will free up memory, so a scheduled daily "pull" with QuickPull or one when your memory is at a certain level will get your memory back up. I schedule a re-boot with QuickPull every morning at 2:00 AM and the device runs fine all day.
Ok I understand this. I have this set up on my phone. I thought that's what the schedule part of your app was for. I was questioning the Monitor option. I assume its the same concept but instead of time its base upon memory? I'm still testing this feature waiting for it to reach the desired Memory.
The schedule part works fine.
Posted from my CrackBerry at wapforums.crackberry.com
Ok I understand this. I have this set up on my phone. I thought that's what the schedule part of your app was for. I was questioning the Monitor option. I assume its the same concept but instead of time its base upon memory? I'm still testing this feature waiting for it to reach the desired Memory.
The schedule part works fine.
Posted from my CrackBerry at wapforums.crackberry.com
You are exactly correct. QuickPull will re-boot on a time-set schedule (as specified by you), and it will also request a re-boot if you have it set to monitor the memory if it gets below a certain specified level.