Well I did a battery pull and it solved the memory problem. I will keep an eye on my memory and see how it acts. I don't know for sure if this log delete caused the up/down memory incident.
Posted from my CrackBerry at wapforums.crackberry.com
Just one more piece of advice to those who do this, the first time
you run a new app, check it again. Some apps that were not in
the list when you stopped the logging will be there after the first
use. I noticed that a couple of times
You can also delete Eventlog.cod in the Java folder and never have to deal with it again.
I have deleted eventlog.cod from java folder but the device is the same as before.... Deleting log files makes the device faster first but deleting eventlog.cod does not make any difference.... that speed does not last forever....
There will be no ill effects from preventing the log from being created. As I posted earlier, it can be deleted completely and everything will be alright. It is merely a diagnostic tool, nothing more.
Posted from my CrackBerry at wapforums.crackberry.com
Can we use Crack uti or another program to just remove the Eventlog.cod file, then reboot. Or does it have to be done before loading OS?
I also cleared my log and set it to not log anything.
To add to what AG said, if you go into menu and then options and then scroll down to the area where the checkboxes are you can just hit menu again and choose hide all types. This way you don't have to uncheck each box.
And remember, if you upgrade (or downgrade) your OS you'll need to do this all over again.
Posted from my CrackBerry at wapforums.crackberry.com
Thanks, with your step by step was a breeze for this Novice BB user who hasn't a clue!
I used Pete6's CrackUtil to copy the eventlog file and noted that it is 2 Kb in size. Deleting the file does free up a trivial amount of memory. On examination, the file is organized as First in, First Out (FIFO). That means it will grow to a maximum size of 2 Kb then recycle the space for the current data.
Removing the file: net_rim_event_log_viewer_app.cod does save 14 Kb. The log is still being created, but if the viewer is not installed, you can ignore it.
I suspect it may be of some use when devices are return for replacement, a way to verify normal operations after they are referbished.
IMHO, the space saved is not worth the effort of clearing the data.
i tried the event log procedure with my metro pcs blackberry, it did make it faster but then all of a sudden my apps failed to connect. browser worked fine but the connection would go in and out whenever it wanted to.
the bad thing is i did it to my sisters verizon blackberry as well and now she is having the same problem. how can i fix this without having to get a replacement phone.
i've done all trouble shooting including wiping out the whole handset and nothing works. . now what?
I recommend not to clear the Event Log. As has been already pointed out here, clearing the Event Log will not free up much space (not a significant amount anyway). Even though you might not have heard of someone using it here, it is an excellent tool to track what applications do. In particular I use it for monitoring certain applications I've granted a suspicious amount of permissions (�berTwitter anyone?) to see if they access the network or do anything else without my consent in the background. For security reasons I highly recommend everyone leave the Event Log as is.
You need to be on the home screen, and hold alt while pressing L G L G.
I'm glad the tune changed towards the end of this thread. I'm with Reed, it doesn't save enough memory to matter, and I have solved issues viewing my own, and looking at others having errors. Dang was I skeered I was going to have to disagree with some who I believe much more in the know than I am.
WAPers do it With A Passion I'm many people's brother, have several BB daughters and sons, but I sure as heck ain't your momma!
* I'm a Survivor Baby!But the dang game fizzled out
Posted from my CrackBerry at wapforums.crackberry.com
You need to be on the home screen, and hold alt while pressing L G L G.
I'm glad the tune changed towards the end of this thread. I'm with Reed, it doesn't save enough memory to matter, and I have solved issues viewing my own, and looking at others having errors. Dang was I skeered I was going to have to disagree with some who I believe much more in the know than I am.
Thanks Badone. I found it out and agree with you it is worth keeping.
B B
Posted from my CrackBerry at wapforums.crackberry.com
I'm 10 days in from my last reboot, cleared the event log, (running log at "information level") and saw no measurable increase in available memory. I leave it running, never bother to clear it, doesn't seem to particularly matter.
I've only really used the event log only once, there was an OS update that broke an app, I was able to copy some of the event log, send it to the app developer, who was able to track down the change in the newer OS and develop an app update to fix the issue.
I actually learned the "event log"tip from the salesman at bestbuy when I bought my cuve 8520. I do it @ least 1-2x a week and it does freeup a lil memory.are there any other logs I can clear to give me even more memory and make my phone lag a lil less?? Like clear out inboxes etc. I've only had my first bb for about 5 months so any info would be VERY helpful!!! Thank you guys!!! Also, I LOVE this site!! VERY informative!!
Posted from my CrackBerry at wapforums.crackberry.com