[Giant Cashew]

I am having the exact same problem. It worked when I installed 1.5.1, but now it does NOT work with 1.5.2. Any seggestions?

Looks like a very limited set of people are seeing error code 5 with the update from 1.4.5 to 1.5.X. I am working on it now.

Although, nothing changed regarding resets between 1.5.1 and 1.5.2, so I'm surprised you didn't see it in 1.5.1.

[barryweiser]

Quick question: Is the new Meterberry update significant enough to warrant an upgrade? I am pretty happy with the old one and recently gotten it to work properly. I am skeptical about undoing everything I did before. Any potential problems people are running into?

What exactly is new with the updated version (STORM)?

Barry

Posted from my CrackBerry at wapforums.crackberry.com

[musikmaker19]

Quick question: Is the new Meterberry update significant enough to warrant an upgrade? I am pretty happy with the old one and recently gotten it to work properly. I am skeptical about undoing everything I did before. Any potential problems people are running into?

What exactly is new with the updated version (STORM)?

Barry

Posted from my CrackBerry at wapforums.crackberry.com

I agree Barry, I love my 1.4.5 and am also worried about updating. I can't decide whether or not to upgrade now or at a later date.

As far as what is new, page one was pretty specific on the details.

[DriftDevil]

could u readd the "clear memory log/batterylog after reboot" option? i dont like having a long log w/o having to clear it all the time

[kcpaynev1]

could u readd the "clear memory log/batterylog after reboot" option? i dont like having a long log w/o having to clear it all the time

i agree with drift

[musikmaker19]

could u readd the "clear memory log/batterylog after reboot" option? i dont like having a long log w/o having to clear it all the time

This was taken away with the upgrade? I'm DEFINITELY not upgrading then. I loved the fact that my QuickPull cleaned up for a fresh log every day.
Hmmm....me thinks that was dirty sounding.
At any rate, I loved being able to see if any new/recent apps were making unwanted changes to memory/battery via the log, so it would be necessary to re-implement this feature.

[Simonintx]

i agree with drift

i agree as well

[TaZ52083]

Me to

Posted from my CrackBerry at wapforums.crackberry.com

Posted from my CrackBerry at wapforums.crackberry.com

[Giant Cashew]

could u readd the "clear memory log/batterylog after reboot" option? i dont like having a long log w/o having to clear it all the time

We removed this feature because we felt it was redundant for the following reasons:

1. You can always view the last time your phone started up in the log with the "Startup" entry. The Startup entry also shows how much memory was reclaimed or how much battery was consumed by rebooting. You don't get this information if you clear the log on startup.

2. The logs are a fixed size, so there is no concern about them filling up forever and consuming all of your phone's memory. New entries overwrite old ones.

3. You can clear all or part of the log manually.

Did you use this feature for some other purpose? There is no loss of information.

We will consider adding it back in based on user feedback though.

At any rate, I loved being able to see if any new/recent apps were making unwanted changes to memory/battery via the log, so it would be necessary to re-implement this feature.

You don't lose this ability by removing the clear on startup feature. The only difference is that entries before the "Startup" entry and entries prior to it are visible. You can ignore them if you want.

[musikmaker19]

But....but.....but......

Damn. I feel like an *****. Maybe we're ocd and loved that feature!!! lol

[musikmaker19]

it bleeps i*d*i*o*t?

[oldskl]

running latest update 1.5.2 and have had since 1.4.5 and like the app and updates seem good kinda streamlined a few things/ removed but not sure if any one else experiencing this but long lag when opening app from icon screen and when closing app just seems slower anyone else getting this




and yeh change log would be great .......

[rlmesq]

Cashew,

The changes to the interface were cool once I figured them out.

Since you've added signal strength, how about a rotating icon for signal? That would allow minimalist themes that could dispense with the usual battery and signal icons.

Posted from my CrackBerry at wapforums.crackberry.com

[Giant Cashew]

running latest update 1.5.2 and have had since 1.4.5 and like the app and updates seem good kinda streamlined a few things/ removed but not sure if any one else experiencing this but long lag when opening app from icon screen and when closing app just seems slower anyone else getting this




and yeh change log would be great .......

I haven't heard anyone report this. You may want to try uninstalling, rebooting, and reinstalling.

Change log is always on the MeterBerry website.

[topdogg_1]

I am having an issue with version 1.5.2 on my Storm. I uninstalled 1.4.5 and installed 1.5.2 and now when I try to do a device reset, I get an error code 5 message.

After installing, I checked the permissions to ensure all are allow and even did a manual battery pull but Device Reset is still not working.

Thanks in advance for any help.

I'm having the same issue (error code 5). It's a clean install not an updgrade on a replacement phone. I'm running .148

[TaZ52083]

No issue with me about error code 5.

[moviemogul]

Cashew, we need an update for those running 5.0, please

[Giant Cashew]

Cashew, we need an update for those running 5.0, please

We did look into a fix for the device reset feature in OS 5.0, but 5.0 doesn't behave like 4.7, either because of bugs or changes to the API, which isn't published yet. We could probably come up with a fix/workaround for the current leaked version of 5.0, but it would likely get "broken" again in the next leak. Once 5.0 becomes more stable and/or the API is published by RIM, we will revisit it.

[FineWolf]

We did look into a fix for the device reset feature in OS 5.0, but 5.0 doesn't behave like 4.7, either because of bugs or changes to the API, which isn't published yet. We could probably come up with a fix/workaround for the current leaked version of 5.0, but it would likely get "broken" again in the next leak. Once 5.0 becomes more stable and/or the API is published by RIM, we will revisit it.

Actually, it's more of a question of "it ain't running at all" versus "the reset doesn't work".

[moviemogul]

Cashew, it doesn't run at all man. I'm not worried about the reset, I can't get the dang thing to start

[Giant Cashew]

Cashew, it doesn't run at all man. I'm not worried about the reset, I can't get the dang thing to start

Ah, I see some reports it doesn't run with the 5.0.0.191 version released today. I will look into it. But like I said, the 5.0 API isn't published, so troubleshooting problems is basically a guessing game.

[Shay D. Life]

Hey GC,
Is there a way to reapply the action that the logs automatically clear on restart?, I hate having to physically go into each log just to delete the prior day.

[Giant Cashew]

Hey GC,
Is there a way to reapply the action that the logs automatically clear on restart, I hate having to physically go into each log just to delete the prior day.

No. Our justification for removing it is here. If you have any feedback, I would be happy to hear it.

http://forums.crackberry.com/f134/me...ml#post3442378

[Shay D. Life]

No. Our justification for removing it is here. If you have any feedback, I would be happy to hear it.

http://forums.crackberry.com/f134/me...ml#post3442378

Cool, I guess I'll just have to continue to do it manually.

[Giant Cashew]

Cool, I guess I'll just have to continue to do it manually.

We are always striving to better understand how our customers use our application.

May I ask why you wish to clear the log daily, when the "Startup" entry indicates when your phone was last reset, and new entries are at the top of the log above the "Startup" entry? Is it just a matter of not wanting to look at old entries?