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?
That was my case, the only time I really need to see the prior days are when I'm testing a theme or an app. But I really have no problem with doing it manually. Thanks for the quick response.
That was my case, the only time I really need to see the prior days are when I'm testing a theme or an app. But I really have no problem with doing it manually. Thanks for the quick response.
Thanks. We may consider adding the "Clear on startup" option back in based on customer feedback.
Any idea for an update that would fix meterberry for 5.0.191?
Posted from my CrackBerry at wapforums.crackberry.com
As you may have noticed, the application permissions interface has completely changed with 5.0. When MeterBerry starts up, it checks if the permissions it requires are set to Allow. I believe this what is causing the exception error on 5.0.0.191.
We are looking into it, but the API for 5.0 isn't published, so there's really no way to troubleshoot or fix it, short of guessing.
We want to avoid having to "fix" MeterBerry every time RIM breaks it with a new interim, leaked, beta OS.
Last edited by Giant Cashew; 08-30-09 at 12:47 PM.
I'm trying to think of a reason why one would not want to reset on a specific day.
this doesnt matter to me since i restart every few days. but im all for adding the option back to clear logs on startup since i really dont like looking at past days unless i need to.
As you may have noticed, the application permissions interface has completely changed with 5.0. When MeterBerry starts up, it checks if the permissions it requires are set to Allow. I believe this what is causing the exception error on 5.0.0.191.
We are looking into it, but the API for 5.0 isn't published, so there's really no way to troubleshoot or fix it, short of guessing.
We want to avoid having to "fix" MeterBerry every time RIM breaks it with a new interim, leaked, beta OS.
Yeah I don't blame you. I can imagine the amount of time that goes into "fixing" meterberry everytime a beta OS leaks. We all appreciate the hard work.
Posted from my CrackBerry at wapforums.crackberry.com
If we add the option to clear the logs on startup, would a single option that clears all the enabled logs suffice? Or would you prefer each log (1, 2, and 3) have its own option to clear on startup?
If we add the option to clear the logs on startup, would a single option that clears all the enabled logs suffice? Or would you prefer each log (1, 2, and 3) have its own option to clear on startup?
a single option would be fine by me. what ever is easier
If we add the option to clear the logs on startup, would a single option that clears all the enabled logs suffice? Or would you prefer each log (1, 2, and 3) have its own option to clear on startup?
So that it's easier (not saying that anything isn't easy for you, you invented the app), I would say the single option as it wouldn't really make a lot of sense to keep anything from the prior day without keeping it all.
