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

Help leaking internal memory

agentc13 said:
I was thinking along those lines, just didn't know exactly what would be doing it (like the debugging!). Thanks for clarifying a bit!



I am sure plenty of people do. There was a poll in the ATR section, I think a decent number used Froyocream which is stock based. I know others do as well. And then there are people who don't know how to change it off stock.
Click to expand...

so if an official update comes out and I update and I have a rooted phone will it brick or mess up my phone?.
 
luis9000 said:
so if an official update comes out and I update and I have a rooted phone will it brick or mess up my phone?.
Click to expand...

At this point, I can't tell you either way. You can unroot your phone though, so I wouldn't worry about it :). Especially since there is no word on any updates, and there may never be one :(. At this point is it purely hypothetical.
 
luis9000 said:
so if an official update comes out and I update and I have a rooted phone will it brick or mess up my phone?.
Click to expand...

IF and I mean IF an official update came out and you decided to update without unrooting the most that it would do (i'm assuming here i've never had an official update lol) would be to just overwrite the OS so it may overwrite everything on the phone or keep user data meaning depending on how they work it may or may not overwrite the fact that your rooted and that's about it... Also bricking it I doubt that would happen... Especially with an official update...
 
luis9000 said:
so if an official update comes out and I update and I have a rooted phone will it brick or mess up my phone?.
Click to expand...
marc12868 said:
IF and I mean IF an official update came out and you decided to update without unrooting the most that it would do (i'm assuming here i've never had an official update lol) would be to just overwrite the OS so it may overwrite everything on the phone or keep user data meaning depending on how they work it may or may not overwrite the fact that your rooted and that's about it... Also bricking it I doubt that would happen... Especially with an official update...
Click to expand...

I know other phones can have an issue with that. It isn't a bad question. But I don't think this phone is brickable. I haven't seen it yet! And it is not something you should worry about now anyway. :D
 
luis9000 said:
what is eating up my memory than??
Click to expand...

apps allocating cache... moving things around... Hmmm how to say it... Basically moving "blocks" around to pack things together better... So your memory is going up and down as it moves things to work better. I don't know how else to really explain... I can see it in my head... Then again i'm more technical so... yea :/

ninjaed by agentc13!!!!!! But yea it's just what b_randon said
 
Yeah if you go in and look with root explorer in the /data partition(which is where apps and app data as well as various system data is stored) there a debugging dump files(a lot like logcat dumps) and some can get pretty big. Also aside from apps caching information the system process use the data partition RI store various things. As long as it doesn't go from like 650mb to 400mb overnight its no big deal.

And yeah a memory leak would be better suited to term a poorly coded app that hogs up RAM(random access memory) which is temporary memory used by the cpu to store information before ans after it is processed. This would be indicated by have very little free RAM. ROM is what you are talking about, which is where things are permanently stored on the phone(the os files on the /system partition, apps and user data on the /data partition(this is the one your worried about) as well as the kernel image and recovery image and radio files on various partitions)
 
I had the same thing happen (with stock, not rooted). I had maybe 120 apps, most on the SD card. All my defaults in programs was "save to a SD card". It happened fast & furious. In several days my internal memory went from 630mbs to nil. I couldn't receive texts even. It was awful. I decided not to root. I did a hard reset & haven't had any problems since. The reason I am posting this is to let you know it happens. It's not just you and you probably didn't do anything to cause it. Android is far from perfect. But it's nice to know you can easily start from scratch whenever you need, as long as you backup your data to the SD card. And if you're rooted, you'll likely find one ginormous file which grew out of control due to an error in code. Good luck. It'll work out. :-)
 
Just solved same problem with internal storage. From the root navigate to /data, there will be multiple files beginning with alog*. I had one in particular named alog_events that was over 700MB. I deleted it with no problems.

Can someone comment why this file is created and how to prevent it from growing so large in the future.
 
gatlanta said:
Just solved same problem with internal storage. From the root navigate to /data, there will be multiple files beginning with alog*. I had one in particular named alog_events that was over 700MB. I deleted it with no problems.

Can someone comment why this file is created and how to prevent it from growing so large in the future.
Click to expand...






Answered above :)
b_randon14 said:
Yeah if you go in and look with root explorer in the /data partition(which is where apps and app data as well as various system data is stored) there a debugging dump files(a lot like logcat dumps) and some can get pretty big. Also aside from apps caching information the system process use the data partition RI store various things. As long as it doesn't go from like 650mb to 400mb overnight its no big deal.
Click to expand...
 
sfdreamsla said:
I had the same thing happen (with stock, not rooted). I had maybe 120 apps, most on the SD card. All my defaults in programs was "save to a SD card". It happened fast & furious. In several days my internal memory went from 630mbs to nil. I couldn't receive texts even. It was awful. I decided not to root. I did a hard reset & haven't had any problems since. The reason I am posting this is to let you know it happens. It's not just you and you probably didn't do anything to cause it. Android is far from perfect. But it's nice to know you can easily start from scratch whenever you need, as long as you backup your data to the SD card. And if you're rooted, you'll likely find one ginormous file which grew out of control due to an error in code. Good luck. It'll work out. :-)
Click to expand...

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.
 
i installed root explorer and i went to data .... i see alot of alog files and they are numbered alog1 2 3 and it keeps going there is also a alog events can i delete those files ????? will it doe something to my phone if i delete it???
 
luis9000 said:
what is root explorer for anyway?
Click to expand...

to be able to access the root of the phone's flash memory... There are few file managers that have the capabilities to read and write to the flash memory (root explorer and es file manager are the only 2 I think).
 
marc12868 said:
to be able to access the root of the phone's flash memory... There are few file managers that have the capabilities to read and write to the flash memory (root explorer and es file manager are the only 2 I think).
Click to expand...


i installed root explorer and i went to data .... i see alot of alog files and they are numbered alog1 2 3 and it keeps going there is also a alog events can i delete those files ????? will it do something to my phone if i delete it???
 
luis9000 said:
i installed root explorer and i went to data .... i see alot of alog files and they are numbered alog1 2 3 and it keeps going there is also a alog events can i delete those files ????? will it do something to my phone if i delete it???
Click to expand...

I think you can delete them with no problems... or just delete the ones that are huge and run the app that they're linked with and see if there are any problems... I don't think it will create any problems though...
 
gatlanta said:
Partially answered. So how do I prevent alog_events, which in my case was 700MB+, from growing so large?
Click to expand...

True, sorry, don't think you can prevent it if it is happening. Just deleting them should help when they get that large. It will have to be a process you repeat from time to time.
 
luis9000 said:
i installed root explorer and i went to data .... i see alot of alog files and they are numbered alog1 2 3 and it keeps going there is also a alog events can i delete those files ????? will it do something to my phone if i delete it???
Click to expand...

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.
 
luis9000 said:
i installed root explorer and i went to data .... i see alot of alog files and they are numbered alog1 2 3 and it keeps going there is also a alog events can i delete those files ????? will it do something to my phone if i delete it???
Click to expand...

Using yaffs explorer I saw alog_events in /data had a file size over 700MB, I deleted about a week ago with no problems. Haven't tried deleting the other alog* files as i had no need after clearing over 700MB+ of internal memory by removing that one file.
 
gatlanta said:
Using yaffs explorer I saw alog_events in /data had a file size over 700MB, I deleted about a week ago with no problems. Haven't tried deleting the other alog* files as i had no need after clearing over 700MB+ of internal memory by removing that one file.
Click to expand...

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
 
You must log in or register to reply here.
Back
Top Bottom