storm version of it works just fine on my tour. have been running it since day one. also have my storms version of simplweather, nintaii, and next running.
Storm version works on my Tour too. I did have one instance of an "Error Code 4" (whatever that means) on a scheduled reset, but other than that, it's been great for the past 3 weeks.
It works fine. But remember the storms app memory is based at 128 mb while we have 256. So if you have say 118 mb free it will say 92%. Still works great though
Posted from my CrackBerry at wapforums.crackberry.com
It works fine. But remember the storms app memory is based at 128 mb while we hsve 256. So if you have say 118 mb free it will say 92%. Still works great though
Posted from my CrackBerry at wapforums.crackberry.com
hmmm.. so the info that it will provide is not accurate being that it is basing the memory off of 128 rather then 256
It works fine. But remember the storms app memory is based at 128 mb while we hsve 256. So if you have say 118 mb free it will say 92%. Still works great though
Posted from my CrackBerry at wapforums.crackberry.com
Running v1.4.5 on my Tour. Works great for battery life, media card memory and memory changes, but does show 128 MB of application memory (as noted above).
How much of a memory change is considered a leak? 1 MB? 5 MB? Any? Any way to figure out what's doing it?
Not totally. For many people, including me, memory changes are more important than total memory available.
I know this, as I am in the same boat as you. However, I was just pointing out a simple "bug" if you may in the program. (Not typically a bug as this was how it was written) Just putting it out there so people don't get too excited lol.
Running v1.4.5 on my Tour. Works great for battery life, media card memory and memory changes, but does show 128 MB of application memory (as noted above).
How much of a memory change is considered a leak? 1 MB? 5 MB? Any? Any way to figure out what's doing it?
I don't loose more than 5MB. I boot at 125 and it'll stay over 120 all day. (I still do scheduled resets as the storm got me in that habit)
I know this, as I am in the same boat as you. However, I was just pointing out a simple "bug" if you may in the program. (Not typically a bug as this was how it was written) Just putting it out there so people don't get too excited lol.
For sure, I was agreeing with you . I was ignorant of the bug until you pointed it out. Frankly, I was paying attention to the memory change so much, that the % of memory was totally ignored by me.
. I was ignorant of the bug until you pointed it out. Frankly, I was paying attention to the memory change so much, that the % of memory was totally ignored by me.