.alog filesSupport


Last Updated:

  1. el fuelte

    el fuelte Member

    is there a way to stop it from growing everyday? The files are alog events,alog,alog1 and It keeps going up like alog2 alog 3.... There also one called alog radio what is it and how can I prevent it from growing itts taking a lot of space of my internal storage.. I will apreciate if you guys help me with this issue and tell me if its normal.

    Advertisement
  2. if you dont get answers immediately, thats not a cause for creating two threads..

    http://androidforums.com/motorola-triumph/494084-alog-files.html

    to answer your question. it SEEMS to be a problem lots of people are experiencing in the stock rom. I havent read any info on how to stop it.

    a good idea is to upgrade to TG-Reloaded CyanogenMod 7 ROM. it doesnt have those problems.

    Also, Froyocream sandwich is doing great for me, but its based on stock and I dont know if it also has that problem long term.

    what i do know is miui and CM7 ran for over a month each on my phone and i never saw that issue.

    if you dont want to do that. just keep deleting the logs.
  3. agentc13

    agentc13 Daleks Über Alles VIP Member

    They are log files that the stock OS creates. For some reason they don't always get deleted so you have to do it yourself.
  4. ziggy46

    ziggy46 Well-Known Member Developer

    can someone make a init.d script that delets them at bootup? im sure it would be pretty easy to do :D
  5. el fuelte

    el fuelte Member

    what is that?
  6. agentc13

    agentc13 Daleks Über Alles VIP Member

    Why don't you give it a shot? ;)
    shmackshmack likes this.
  7. ziggy46

    ziggy46 Well-Known Member Developer

    where are those log files located in the phone?
  8. agentc13

    agentc13 Daleks Über Alles VIP Member

  9. ziggy46

    ziggy46 Well-Known Member Developer

  10. agentc13

    agentc13 Daleks Über Alles VIP Member

    I have no idea, I am running CM7 as well. :D

    I am sure some other folks with that issue can help you out with that. :cool:
  11. ziggy46

    ziggy46 Well-Known Member Developer

    ok i think i might have it...

    try putting this in /system/etc/init.d and reboot. (make sure you have a nandroid backup though! incase this doesnt work)

    30alog_remover

    if it works let me know and i will make it flashable and expand it to delete more of the alog* files...

    as of right now, its set to delete

    alog_events.txt
    alog1
    alog2
    alog3
    alog4
    alog5

    check to see if those get removed :)
  12. agentc13

    agentc13 Daleks Über Alles VIP Member

    Note: You must be rooted to do this, right Ziggster?
  13. ziggy46

    ziggy46 Well-Known Member Developer

    yup :D

    lol ziggster :p
  14. el fuelte

    el fuelte Member



    how you do that?
  15. thangfish

    thangfish Well-Known Member

    Does our stock ROM support init.d scripts?
  16. b_randon14

    b_randon14 Well-Known Member Developer

    I have a script that removes all log files in cluding alog* plog* pmlog* and the logs in data/efslog/OEMDBG_LOG, /data/last_alog, and /data/last_klog. I have ran it on my phone(i put it in system bin and chmod'ed it to 755 so i can just call rmlogs from the terminal, but you can also place the script in /system/etc/init.d and it will run at boot on a kernel with init.d support)

    In total it only cleared up like 15mb on my phone, but I am running a custom version of my bROM(we'll call it 1.0 1/2) and I have managed to get it to where it doesn't dump as many logs on my ROM, by changing a couple xml config files in the ROM(or at least I believe that is what did it lol!) but if you have a bunch of alog files the amount cleared will be monumental. The script deletes anything in /data starting with alog, plog and pmlog, and clears out the folders i mentioned above with the log files.

    What is happening is that as certain events take place, the phone dumps logs of those events to the data partition. I believe this was used in debugging the phone and perhaps was left on by accident when the ROM was released. Most of the files never grow very large, but some of them(most notably the alog files) can grow to be very large.

    Here is the link to the script. Like I said you can either put it in /system/etc/init.d and chmod it to 755 to have it run at boot(must have a kernel that supports init.d scripts) or you can place it in /system/bin and chmod the file to 755 and you can run it simply by opening a terminal and type su then rmlogs. I am including the script in my 1.1 ROM for easy cleaning of log files.

    rmlogs script

    If anyone needs help getting the script copied and the permissions set on it(chmod) then let me know. you must be rooted in order to run the script and to place it and chmod it. For init.d support you need a kernel that runs init.d scripts(just about every custom kernel does)

    @thangfish, its more to do with the kernel, like if you run my kernel on the stock ROM, then init.d scripts can be ran, because my kernel runs init.d scripts on any ROM. pwn's kernel however requires busybox to be installed with the run-parts binary and it has to be installed to /system/bin because of the way he set his init.d support up. I'm not sure about the other kernels.

    And the reason why cm7 and miui don't do this is the way their framework is set up. It's not set up to dump log files all the time. I'm sure this was a blunder by Motorola in there hurried release of this phone.
    civicscootin, ziggy46 and thangfish like this.
  17. thangfish

    thangfish Well-Known Member

    So... For the OP's question...
    On stock, there is little that can be done.
    You will need to be rooted at the very least.

    To automatically delete the files, you need to be rooted, with a custom kernel.

    To keep the files from being made to begin with, you need a different ROM.

    Actually, I think I saw a mod that allowed init.d scripts to be run on stock.

    Edit:
    Yes... Here's a link..
    [ADDON] Startup scripts support (init.d support) for Stock ROM/Kernel - xda-developers
  18. ziggy46

    ziggy46 Well-Known Member Developer


    well my script was close.... just a little touchups and it would have been good :p
  19. b_randon14

    b_randon14 Well-Known Member Developer

    Yeah you had it in the right direction! Without being on a stock rom its hard to tell what all files need to be removed lol! I had to edit my script quite a bit before I got all of them gone!
  20. ziggy46

    ziggy46 Well-Known Member Developer

    cool! :)
  21. b_randon14

    b_randon14 Well-Known Member Developer

    Hey I got your keyboards done! If you want I can make a light blue themes one as well for froyocream! And a blacked out one for minimal
  22. ziggy46

    ziggy46 Well-Known Member Developer

    awesome that would be cool! :D thanks :)
  23. redoscar3

    redoscar3 Member

    New user here. Ziggy's YouTube post got me interested in this topic. I have an unrooted MT and don't believe I am experiencing this alog problem. I realize you probably have to be rooted to see the files on the filesystem, but unless I see free memory shrinking significantly, I will assume all is well on my MT.

    My comment is, is there any chance that these alog files are being created and appended due to some particular installed program that is causing a lot of errors? I understand that perhaps the original Motorola developers forgot to remove the debugging flags before they compiled the official ROM, but unless there are errors or comments to log, not much would really happen.

    Just a thought on my part. And thanks to Ziggy for getting me interested enough to register and participate.

    Red
    ziggy46 likes this.
  24. mhlsilverdale

    mhlsilverdale Well-Known Member

    Edited: okay, I now realize who I'm posting a reply to; I'm new here, sorry. I realize you wanted the location for a script. However, I'll leave my original post since it may help others.
    Location of /data block on Triumph from: cat /proc/mounts
    /dev/block/mmcblk0p8 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
    /data

    #Terminal Commands#
    su
    mount -o remount,rw -t yaffs2 /dev/block/mtdblk8 /data
    cd /data
    rm alog_events
    exit

    Once deleted, the OS will recreate it again but it will start out much smaller.
    I was able to gain back 600MB of internal storage after running this.

    **** To delete system log files your phone must be rooted ****


    Mark
  25. b_randon14

    b_randon14 Well-Known Member Developer

    I have found the alog and other log file issues to be a two part problem. Part is in the rom and part is in the kernel. On bROM o had found some configuration files that were on the stock rom that had a by change of debugging entries turned on, well I disabled all those in vertical early versions of bROM and had it to where they would be huge files but you would still get a couple MB of log files accumulated. Then I found some entries in the kernel config file where more debugging was enabled, so with bROM and my latest kernels, no align files.

    The lucky thing about the triumph is that it cones basically rooted, with a sudo such binary in xbin and they left the system being mounted as read/write in the kernel so even without rooting this phone with like gingerbreak or something, you can gain root access from a terminal emulator and can delete those log files like that!

Share This Page