• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help leaking internal memory

I wasn't saying that it had anything to do with being rooted. If you're not rooted you can't fully explore your internal memory & delete log files. If you're rooted you can. I am not sure how you got that I thought this error of a growing file/space running out for no apparent reason in itself had anything to do with being rooted or not from my post. The SOLUTION is different if you're rooted or not. Also I never recommended a hard reset. I just mentioned I had done one. It wasn't the end of the world when I did. I chimed in because some of the comments (not yours) were getting rude and really just unhelpful to the original poster and I wanted to let him know that the same thing happened to me - he wasn't alone. That was all my post was saying.
So far so good. I have over 400mbs of internal memory and it's not shrinking... :)
agentc13 said:
Being rooted has nothing to do with this. It happens to people who have rooted their phones and those who have not.

Also a factory reset is not always a permanent solution. If it happens again, will you just reset again? I personally wouldn't want to lose all my custom settings and data multiple times.
Click to expand...
 
luis9000 said:
where do those files come from?? I don't think its safe to delete those files..... Why would the phone habe them th
..? Mabe its important
Click to expand...

I'll add my two cents and then defer to more knowledgeable persons on this board.

If you don't think it's safe then you shouldn't do it. Although, I have had no problem since deleting the alog_events file on my phone. There could be many reasons such a file would exist that wouldn't affect the operation of the phone, namely logging certain events or actions for later review or debugging. It seems there may be an errant process that isn't purging this file periodically.

From my read, alog* files are some type of android log files, not sure what process is creating them. From googling, other Triumph owners have reported problems with the alog_events file growing very large as well as numerous other alog* files of about 8MB. Only resolution I've seen is to delete.

As a precaution before trying the deletion solution, you should copy the targeted file to your SD before deleting so you can replace if needed. In my case I only deleted the one large file named alog_events rather than deleting the 20 other alog* files that were about 8MB each.
 
sfdreamsla said:
I wasn't saying that it had anything to do with being rooted. If you're not rooted you can't fully explore your internal memory & delete log files. If you're rooted you can. I am not sure how you got that I thought this error of a growing file/space running out for no apparent reason in itself had anything to do with being rooted or not from my post. The SOLUTION is different if you're rooted or not. Also I never recommended a hard reset. I just mentioned I had done one. It wasn't the end of the world when I did. I chimed in because some of the comments (not yours) were getting rude and really just unhelpful to the original poster and I wanted to let him know that the same thing happened to me - he wasn't alone. That was all my post was saying.
So far so good. I have over 400mbs of internal memory and it's not shrinking... :)
Click to expand...




Yeah, the part that had me thinking that was this:
sfdreamsla said:
And if you're rooted, you'll likely find one ginormous file which grew out of control due to an error in code.
Click to expand...
Sounds like you understand what root access is, but that threw me because it doesn't change code (just access)

I may have misunderstood your intent. And like you said, you cleared it up and shared. Wasn't trying to squash that, just point out it may not be a permanent solution. :)
 
luis9000 said:
where do those files come from?? I don't think its safe to delete those files..... Why would the phone habe them th
..? Mabe its important
Click to expand...







gatlanta said:
I'll add my two cents and then defer to more knowledgeable persons on this board.

If you don't think it's safe then you shouldn't do it. Although, I have had no problem since deleting the alog_events file on my phone. There could be many reasons such a file would exist that wouldn't affect the operation of the phone, namely logging certain events or actions for later review or debugging. It seems there may be an errant process that isn't purging this file periodically.

From my read, alog* files are some type of android log files, not sure what process is creating them. From googling, other Triumph owners have reported problems with the alog_events file growing very large as well as numerous other alog* files of about 8MB. Only resolution I've seen is to delete.

As a precaution before trying the deletion solution, you should copy the targeted file to your SD before deleting so you can replace if needed. In my case I only deleted the one large file named alog_events rather than deleting the 20 other alog* files that were about 8MB each.
Click to expand...

You should be fine to delete them. If you don't like that idea, I recommend unrooting and then doing a factory reset. If you wan to try it, I recommend getting CWM on your phone so you can do a backup first.
 
agentc13 said:
Do you have CWM on your phone? You could make a backup and then try it out. If it caused issues you can restore the first backup and be in the same shape as when you started.
Click to expand...

where do those files come from?..? Is it safe to delete those files?. Why does the phonw make those files??
 
agentc13 said:
It's a recovery for your phone that allows you to make backups and install ROMs.
Click to expand...

I cleared the alog events idont have problems yet..... But I went to root explorer and than I went to data and the alog events was there again it had 16 mb and now its groing bak it has so far 1 mb
 
luis9000 said:
I cleared the alog events idont have problems yet..... But I went to root explorer and than I went to data and the alog events was there again it had 16 mb and now its groing bak it has so far 1 mb
Click to expand...

You may have to do it multiple times. 1mb or 16mb should not be a worry. Ideally the system will delete the files before they get huge. As stated before they are log files that the OS/apps make and use. Having them there isn't bad unless they get huge.

If they get huge, it is possible you have an app that is causing that behaviour.
 
agentc13 said:
You may have to do it multiple times. 1mb or 16mb should not be a worry. Ideally the system will delete the files before they get huge. As stated before they are log files that the OS/apps make and use. Having them there isn't bad unless they get huge.

If they get huge, it is possible you have an app that is causing that behaviour.
Click to expand...

so I only have to delete the alog events or all of them there's another one called alog radio
 
Yes those files are safe to delete. This phone's operating system is setup to periodically dump logcat, kmesg, and radio logs out to files in /data which can grow to be white large. They are there I assume for when they were debugging the operating system and maybe they forgot to disable it.
Also Roms like cm7 don't do this as it is not setup too.
 
b_randon14 said:
Yes those files are safe to delete. This phone's operating system is setup to periodically dump logcat, kmesg, and radio logs out to files in /data which can grow to be white large. They are there I assume for when they were debugging the operating system and maybe they forgot to disable it.
Also Roms like cm7 don't do this as it is not setup too.
Click to expand...

so can i delete all the alog files and the radio ones and ill have no problem??? but if i do delete them they will come bak right???:confused::D
 
luis9000 said:
so can i delete all the alog files and the radio ones and ill have no problem??? but if i do delete them they will come bak right???:confused::D
Click to expand...

Yeah. Probably.
Like I said, unless those files are getting quite large it isn't that big of a deal. They don't hurt anything if you don't need the space for something else.
 
Is it possible to see and delete these files if your phone is not rooted?
 
luis9000 said:
Can a rooted android phone get virus or malware????? if yes what will it do?????
Click to expand...

I know there is Malware that can get on your phone. It is usually not an issue unless you are pirating apps or going to shady market alternatives. When I get back to my computer I will link a post to help you protect yourself from that sort of thing. I personally don't think anti-virus helps on phones yet.
 
luis9000 said:
I sometimes use a certain site where you can get free paid apps there you meen that market??
Click to expand...

That is one of the shady markets... If you are getting paid apps for free (except through amazon appstore's paid app of the day), its going to ba most likely a pirated version that can contain malware and viruses... And virus protection right now does nothing... There have been tests and most do nothing or very little.
 
I use the Google and Amazon marketplace. If an app developer asks for payment, then I feel I should pay them for their work if I want that app. I know of one other apparently legit site (getjar) that has a different model for paid apps, but it doesn't update the apps like the Google or Amazon marketplace. So I don't use that one, but apparently they are okay.

I would tell you to avoid that site. From everything I know it is piracy/warez. As a general rule unless it is approved by the dev a paid app should not be available for free.
 
You must log in or register to reply here.
Back
Top Bottom