Messages have been sent out. Thanks to everyone for participating. I'll update here with screenshots for newer builds. I will also send out new builds to the beta testers when they are completed.
Suggestions for improvements are still welcome, and I hope to extend the beta to different types of BlackBerrys in the near future.
Sent you a PM regarding OTA hosting for your updates and such. Let me know if you're interested. Ask CheetahAce for a reference if you'd like I did it for his QuickLaunch application during beta mode and still using it as a support site in case the purchase sites don't work.
Sent you a PM regarding OTA hosting for your updates and such. Let me know if you're interested. Ask CheetahAce for a reference if you'd like I did it for his QuickLaunch application during beta mode and still using it as a support site in case the purchase sites don't work.
I'm looking into this. Will message you tomorrow with details
Posted from my CrackBerry at wapforums.crackberry.com
I installed log maid and rebooted the phone. The first few tries at getting this program to launch resulted in a java error. I waited a few minutes and tried again and the program has worked ever since with no more error messages.
I will set Capture It to a side key and if it happens again I will post a screen shot.
I installed log maid and rebooted the phone. The first few tries at getting this program to launch resulted in a java error. I waited a few minutes and tried again and the program has worked ever since with no more error messages.
I will set Capture It to a side key and if it happens again I will post a screen shot.
I also installed logMaid after installing BBMem and didn't receive any errors, everything has run smoothly for me.
I installed log maid and rebooted the phone. The first few tries at getting this program to launch resulted in a java error. I waited a few minutes and tried again and the program has worked ever since with no more error messages.
I will set Capture It to a side key and if it happens again I will post a screen shot.
Did you get the "illegalArgumentException"? If so, if you figure out how to reproduce this result, I'll send you a debug version without the percentage bars. Then we can figure out which one is faulting. This happens when the memory reported does not fall in the correct bounds for the progress bar.
Well, it seems I've hit a bit of a brick wall. There does not appear to be any reasonable way to get the memory statistics per program in the api, and because BB runs on java, its very difficult (impossible?) for me to manually access and count the memory used in the virtual machine. As of now, I simply have a more detailed overview of how the total memory is being used (see screenshot - note: screenshot was taken in a VM, so the memory in pic does not reflect real BBStorm usage). So, I was thinking that I would release the program (in its beta state) as a kindof preview if there is interest.
Oh, and thanks for the comments so far, I'm looking into some of the suggestions
~King
Hi. Your program looks good keep it up. You're going to hit a looooooot of brick walls working with the JDE and the rim OS. And by a lot I mean a LOT. As you probably know they don't allow access to many things on the device. I doubt you'll be able to get the memory cleaner. I tried many many times and many many ways but no good. If you do though that would be so awesome.
Hi. Your program looks good keep it up. You're going to hit a looooooot of brick walls working with the JDE and the rim OS. And by a lot I mean a LOT. As you probably know they don't allow access to many things on the device. I doubt you'll be able to get the memory cleaner. I tried many many times and many many ways but no good. If you do though that would be so awesome.
Yea, I highly doubt I'm gonna get a per-program memory breakdown. But, the memory cleaner is in the package net.rim.device.api.memorycleaner. there is a daemon in there that you can use to run the cleaner... The cleaner is not what people think... It simply writes zeroes to the specified portions in memory. Its only there to get rid of sensitive data, not to manage the memory in any way.
Yea, I highly doubt I'm gonna get a per-program memory breakdown. But, the memory cleaner is in the package net.rim.device.api.memorycleaner. there is a daemon in there that you can use to run the cleaner... The cleaner is not what people think... It simply writes zeroes to the specified portions in memory. Its only there to get rid of sensitive data, not to manage the memory in any way.
I saw that mem cleaning daemon. Is that the actual memory cleaner?
Have you verified this?
Please let me know. thanks.
Did you get the "illegalArgumentException"? If so, if you figure out how to reproduce this result, I'll send you a debug version without the percentage bars. Then we can figure out which one is faulting. This happens when the memory reported does not fall in the correct bounds for the progress bar.
I believe that is what it was. I installed log maid, restarted the Storm, then hit the icon for the memory viewer. That is when I had it happen. It has not happened since, though.
Long shot, but could I have hit it at the exact time log maid was doing it's thing and maybe that is what caused it?
What must have happened is when you restarted your storm, there was more free memory than allocated in one category. I've fixed the crash for that, so when I send out the next build, it shouldn't be a problem
Well, I've been working on the program a bit lately, and I've added some new functionality. First off is auto-refresh. The program will update every 30 seconds or so, and secondly is a histogram to display usage over time. This tracks the first 3 categories, so you can see how your memory is being used when new programs run. Here's a little pic. Still some bugs to work out, but beta testers will get their hands on it within the coming days