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

Help Internal Memory getting ate up FAST

Pretty recently I noticed my internal memory was staying at about 30-35. I tried clearing a few things & even deleted some stuff in hopes of freeing more (I already use a task manager for running programs & I always immediately move ALL of my programs to SD card), but still didn't help much at all. Then in last few days my internal has even gotten alot less. I haven't added anything else and I've made sure to clear every cache I can find in my programs. Even when I start my phone it only has approximately 22free now. What is my best way to fix this problem?
 
Pretty recently I noticed my internal memory was staying at about 30-35. I tried clearing a few things & even deleted some stuff in hopes of freeing more (I already use a task manager for running programs & I always immediately move ALL of my programs to SD card), but still didn't help much at all. Then in last few days my internal has even gotten alot less. I haven't added anything else and I've made sure to clear every cache I can find in my programs. Even when I start my phone it only has approximately 22free now. What is my best way to fix this problem?

If you're running stock Froyo, it's probably a known bug that creates ever-enlarging log files. You need to root to delete them periodically or switch to a custom ROM...

Do a search in the forum & you'll find several threads on this...
 
Its been rooted with using terminal emulator. I just don't know what files to delete or what to do.

Using ES file explorer, (you must give it root access, and allow system write access) navigate to /Data and look for alog files. Check how big they are.
If they have gotten huge, just delete them.

They will be remade and start to grow again.
After they are remade and are still small, you can change permissions by long pressing. Remove WRITE access and they wont grow anymore.

If that doesn't make sense to you, post back and I'll try to walk you through it.

If you don't see any really large alog files, you have something else going on.
 
Somehow Terminal Emulator quit working (suddenly would say sudo: not found) so I installed gingerbreak for root. I enabled root access in es file explorer & mount file system as writable. I searched data for alog. "Last alog" folder is 4mb, "alog events" 635mb, "alog", "..system", & "..radio" files are about 8mb each, and alot of "last alog radio, ..system, ..main",etc run between about 145kb - 60kb.
Would u recommend deleting all? Do I need to go back in options before I leave file explorer and undo root access & mount as writable?

Also could you possibly tell me also how I can uninstall/delete the bloatware I don't want?

THANK YOU VERY VERY MUCH! You have been a Great help
 
635mb! That one definitely has to go. That one will fix your issue, but if it was me, I'd get rid of all of them just because. Don't forget to check back after at least one reboot (maybe tomorrow?) And remove the write permissions from any that have returned.

As far as removing bloatware... There are several ways. I would suggest using Titanium Backup or System Tuner. Both have free versions and both are extremely useful, now that you are rooted.

You can do it manually, using ES File Explorer too, but some apks may have confusing names, compared to the actual app name. Most will be in the system/app/ directory. There may be some in /hidden too... Can't remember off hand.

System Tuner and Titanium Backup will list them by app name and also both will backup the app before uninstall... Just in case you get rid of something important. Be careful.

Edit:
I always leave root access and system writable enabled in ES File Explorer. If no one else is using your phone, I wouldn't worry about it. If you feel better disabling them, go ahead. No big deal either way, really.
Have fun man.

Edit no. 2:
I did see your other posts about your issues with sudo/su/terminal emulator. Don't know what to say about that, but the most important thing is to install CWM recovery so you can back up your stock ROM as a Nandroid backup before you start uninstalling crap. That way you can always restore a working stock ROM. Instructions are on the sticky, but basically it involves booting into "boot loader" mode, backing up/renaming the old recovery and copying the new one using your computer. Don't touch anything else in that directory and all will be fine. That's where people screw up... Messing up (or deleting) the directory.
 
Thank you for the awesome help & advice! Its nice to have instructions simple + exact, yet not make it out like your an idiot for needing the help, lol. Thanks

Any bloatware I remove I will make sure it is on the safe list for removal. I too have noticed alot of programs/files names aren't the exact program name. I'll be very careful not to delete anything I shouldn't.

I know Triumph did finally release a system update (for the original stock) however I understood you have to update it manually. I never have gotten any update on this. Do I need to update it?
 
I really don't know what was updated.
Haven't heard anything about it, honestly.
You'll probably be running cm7 or something soon anyway. :D
 
I really don't know what was updated.
Haven't heard anything about it, honestly.
You'll probably be running cm7 or something soon anyway. :D

Agree- even if you want to stick with froyo, go with something like the U9000 ROM- who wants to deal with having to constantly monitor those log files. I think g60madman also came up with a cleaned-up "stock" ROM, kind of like the way it should have been delivered & you could go with that if you're dedicated to the stock ROM.
 
I think I'm gonna probably try cm7. I don't have time right now (nor do I have access to a computer right now) but if I'm able to I will try tonight.
 
I've seen a few cm7 roms. I've read the initial stuff on them (but of course there are too many posts on their thread to read all of them). I still not sure the difference(s) or if there are much difference or what?! ? Like I know that the thread for the cm7 build (2012-12-28) & cm7-reloaded(update to Tickerguys) that also seems to have alot of posts on. What's the difference or which one is best?? ?
 
I've used them all, as they were developed.
12-28 is the most recent and the one I would recommend.
Functionally, you wouldn't notice much difference. Most notably I guess, would be a little better GPS performance.
Different libraries used to build them, and different dev teams, etc. The most current build will have the most cm7 updates from "upstream" (cyanogen mod).

Make sure you download the appropriate Google app package (gapps) at the same time, as you will have to flash that after you flash the ROM.
 
Back
Top Bottom