Everything is out of memory

[Guest thenext1]

Hi all

I tried to ignore it, but this is getting on my nerves.

I only have 20 apps installed, most of them are less than 500k in size, the others being mainly Facebook (slow piece o'sh*t), adobe reader, google maps (would happily uninstall), Astro, and a game.

But some days ago the phone suddenly started complaining it is low on space and won't go away. In fact the free space (internal flash memory) is less than 20mb.

Why is that? I remember with the Hero, with identically-sized internal memory and same amount of installed apps, I had ~80mb left.

Something has surely eaten out all my internal memory and I see no remedy unless I flash.

I already ran thru my app list and cleared all caches.

Maybe these are some hidden memory dump from the times my phone crashed? (It happened almost ten times on this idiot firmware.)

Now, the last part of the story: out of blue, the fone says the "text message memory" is full and an incoming message was rejected. I even have less than 100 messages because I clear them routinely.

BTW, WTF??? I thought I was freed from this hassle when I ditched my last Motorola phone.

I deleted some messages: no way. Why is that?????

arghhhhhh I'm seriously considering to reflash android 1.6, so fast, so stable

[Guest Delnar_Ersike]

Well, some apps' sizes drastically increase because they use their data as a cache, so you can't empty their caches manually without deleting all the app data (Titanium Backup, for instance, has this problem). If you have the aforementioned app installed, backup all your apps, then remove your apps one-by-one, starting with the ones that take up the most space (Documents to Go and Adobe Reader can be huge). Oh, and don't forget to filter the apps so that all are displayed, not just the apps you downloaded.

As for your "memory dump", I believe whenever Android crashes, a kernel panic "dump" is written onto the SD card, but it doesn't dump anything onto the on-phone storage space. Of course, I'm not that versed in the inner workings of the OS as well as some on these forums, so in case I'm wrong, I'll stand corrected.

By the way, what ROM are you using? And if you aren't using the stock, when you installed the ROM, did you do a full wipe and clear the cache?

Edited August 14, 2010 by Delnar_Ersike

[Guest Rajit]

sounds familiar! which bin and rom are you using??

[Guest L0cu7us]

1.100.39 for sure :D

[Guest Rajit]

1.100.39 for sure :D

which was my guess as well ;p ... with a version earlier than 1.8/1.7.2/xian0.9 .... many of us had the same problems, each of these roms seem to solve it (although im not exactly sure about lcr 1.7.2, but it doesnt make any sense for it not to)

[Guest thenext1]

I use stock 1.100.39 because I don't like modifications.

I flashed the .bin that was linked on this forum using Acer Tool...it should flash the whole phone deleting everything on all partitions, or...?

And for that "sms memory full" problem? I have 15mb free right now and I still can't read the incoming sms because it complains (there are 2 icons, one for teh disk space, one for the sms memory).

Does this rfirmware store SMSs on the sim card?

@Delnar_Ersike: DTG caches everything on a folder on the SD card (what an idiot behavior...). Adobe has no cache I can clear.

I use my phone as an end-user, without root, mods, or smart appz like titanium backup.

I'll run through all system apps but this shouldn't happen in the first place. What should I be on the lookout for?

[Guest dennerjw]

I have over 3000 messages stored on my internal memory using 1.100.39 and Xian v1 :D

[Guest Rajit]

I use stock 1.100.39 because I don't like modifications.

I flashed the .bin that was linked on this forum using Acer Tool...it should flash the whole phone deleting everything on all partitions, or...?

And for that "sms memory full" problem? I have 15mb free right now and I still can't read the incoming sms because it complains (there are 2 icons, one for teh disk space, one for the sms memory).

Does this rfirmware store SMSs on the sim card?

@Delnar_Ersike: DTG caches everything on a folder on the SD card (what an idiot behavior...). Adobe has no cache I can clear.

I use my phone as an end-user, without root, mods, or smart appz like titanium backup.

I'll run through all system apps but this shouldn't happen in the first place. What should I be on the lookout for?

There's your problem!!! 1.100.39 had this problem of creating DxDrm logs which would eventually eat up the whole memory... if your device isn't rooted i don't think you can retrieve the space as the logs are in /data folder which is only accessible on a rooted device (pls correct me if im wrong) If it is rooted just open up the terminal emulator and fire the following commands:

su

rm -f /data/DxDrm/Log*

or to delete them on each reboot just fire:

ins_run rmDxDrmLogs rm -f /data/DxDrm/Log* (haven't tested, don't know if this one works)

But there are better solutions... if you wanna stick with a stock rom, go and flash .63 bin (i think it doesn't have this bug). BUT i strongly suggest you give lcr 1.8 a try, cuz if you do you don't have to flash a new bin (its designed specially for .39) and it solves this and many other bugs... believe me u won't be disappointed! :D

Edited August 14, 2010 by Rajit

[Guest eumate]

There's your problem!!! 1.100.39 had this problem of creating DxDrm logs which would eventually eat up the whole memory... if your device isn't rooted i don't think you can retrieve the space as the logs are in /data folder which is only accessible on a rooted device (pls correct me if im wrong) If it is rooted just open up the terminal emulator and fire the following command

rm -r -f /data/DxDrm

this would free a lot of memory, but it would eventually fill up again... so if you wanna stick with a stock rom, go and flash .63 bin. BUT i strongly suggest you give lcr 1.8 a try, cuz if you do you don't have to flash a new bin (its designed specially for .39) and it solves this and many other bugs... believe me u won't be disappointed! :D

Or just install the patch for 1.100.39 available on acer mobile website.

[Guest Rajit]

Or just install the patch for 1.100.39 available on acer mobile website.

didn't know there was a patch

[Guest thenext1]

Or just install the patch for 1.100.39 available on acer mobile website.

The patch appears under the Liquid E section... i have a 256MB Liquid...

[Guest Delnar_Ersike]

The patch appears under the Liquid E section... i have a 256MB Liquid...

That's because officially, only the Liquid E is supposed to have Eclair. That's the only difference between a Liquid A1 (regular Liquid) and a Liquid E... that, and the RAM. You shouldn't encounter any problems flashing a Liquid E ROM or patch to a Liquid A1.

[Guest thenext1]

There's your problem!!! 1.100.39 had this problem of creating DxDrm logs which would eventually eat up the whole memory... if your device isn't rooted i don't think you can retrieve the space as the logs are in /data folder which is only accessible on a rooted device (pls correct me if im wrong) If it is rooted just open up the terminal emulator and fire the following commands:

su

rm -f /data/DxDrm/Log*

or to delete them on each reboot just fire:

ins_run rmDxDrmLogs rm -f /data/DxDrm/Log* (haven't tested, don't know if this one works)

Only if I can't do it thru the patch :D

But there are better solutions... if you wanna stick with a stock rom, go and flash .63 bin (i think it doesn't have this bug). BUT i strongly suggest you give lcr 1.8 a try, cuz if you do you don't have to flash a new bin (its designed specially for .39) and it solves this and many other bugs... believe me u won't be disappointed! :D

Isn't the .63 bin customized?

ANyway I learned to stay away from the mods with my old Windows Mobile phone, when installing custom roms was the only way to stay updated.

The landscape was grim to say the least; everyone claimed to have solved this and fixed that, but no one finally solved the annoying bugs that originated with the initial hacked WM6 port. The phone was a HTC Universal, and today files are still getting randomly deleted on pulling hte sd card, 3G videocall still doesn't work on WM6, camera still goes haywire pretty often, and the like. I remember of installing "new versions" hacked roms, often with very long (fake?) changelogs, and incurring in bugs I thought were long gone, and getting nervous over that because flashing requires time. Lots of advertisement, but the best supported roms still boil down to a pile of preinstalled utility apps (useless to most of the public), often very CPU-hungry, and myriads of "fixer" apps to fix various bugs of the phone.

So, no custom rom action for me now, thanks ;)

[Guest thenext1]

That's because officially, only the Liquid E is supposed to have Eclair. That's the only difference between a Liquid A1 (regular Liquid) and a Liquid E... that, and the RAM. You shouldn't encounter any problems flashing a Liquid E ROM or patch to a Liquid A1.

Liquid A1 does have an official Eclair rom (1.100.13), just look under that very site.

EDIT: OK I've downloaded the Update.zip and it contains system files, so no problem should arise. But, will I really lose all data on the phone?? umpffffff....

Edited August 14, 2010 by thenext1

[Guest Rajit]

Isn't the .63 bin customized?

ANyway I learned to stay away from the mods with my old Windows Mobile phone, when installing custom roms was the only way to stay updated.

The landscape was grim to say the least; everyone claimed to have solved this and fixed that, but no one finally solved the annoying bugs that originated with the initial hacked WM6 port. The phone was a HTC Universal, and today files are still getting randomly deleted on pulling hte sd card, 3G videocall still doesn't work on WM6, camera still goes haywire pretty often, and the like. I remember of installing "new versions" hacked roms, often with very long (fake?) changelogs, and incurring in bugs I thought were long gone, and getting nervous over that because flashing requires time. Lots of advertisement, but the best supported roms still boil down to a pile of preinstalled utility apps (useless to most of the public), often very CPU-hungry, and myriads of "fixer" apps to fix various bugs of the phone.

So, no custom rom action for me now, thanks :D

No its official.

I understand your problem with these "custom roms", but i would still suggest that don't let past experiences ruin your current experience. If you are gonna flash something and lose all your data, why not give it a try? If you don't like it you can always revert back to stock! There are plenty to choose from. Some like LCR 1.7 focus on features, while others like 1.8 and Xian v1 focus on speed (xian v1 is especially light, but 1.8 is equally fast). The main problem is that there is still no perfect eclair bin made available by acer. Best wishes!

ALSO, 0.39 was also for Liquid (not liquidE). It was taken off the site because of this very bug!!!

Edited August 14, 2010 by Rajit

[Guest Delnar_Ersike]

Liquid A1 does have an official Eclair rom (1.100.13), just look under that very site.

EDIT: OK I've downloaded the Update.zip and it contains system files, so no problem should arise. But, will I really lose all data on the phone?? umpffffff....

Don't know if it's a wipe update: if it is, then yes, if no, it won't wipe your phone. However, because this is official, I think it's a wipe update.

However, this is one of the main advantages of rooting your device: you get access to backup apps like Titanium Backup or ROM Manager.

[Guest thenext1]

No its official.

I understand your problem with these "custom roms", but i would still suggest that don't let past experiences ruin your current experience. If you are gonna flash something and lose all your data, why not give it a try? If you don't like it you can always revert back to stock! There are plenty to choose from. Some like LCR 1.7 focus on features, while others like 1.8 and Xian v1 focus on speed (xian v1 is especially light, but 1.8 is equally fast). The main problem is that there is still no perfect eclair bin made available by acer. Best wishes!

Sorry, I meant "operator-customized" because of the "CUS1" suffix instead of the generic one.

Anyway I'll root for now coz I need my data now! Worse wrecks happen remarkably on time :D

[Guest malez]

which was my guess as well ;p ... with a version earlier than 1.8/1.7.2/xian0.9 .... many of us had the same problems, each of these roms seem to solve it (although im not exactly sure about lcr 1.7.2, but it doesnt make any sense for it not to)

fixed inLCR-S 1.7.3 and LCR-E 1.8

[Guest malez]

Sorry, I meant "operator-customized" because of the "CUS1" suffix instead of the generic one.

Anyway I'll root for now coz I need my data now! Worse wrecks happen remarkably on time :D

Be carrefull with root ! don't use any superboot, it a big s*** when not specially designed for your bin (Yes I know usally I speak in a correct way, but so many user contact me to tell me "my phone does not boot since i have installed a superboot" that i insist.)

Install malez recovery and use it to root your phone (if you still want to stay on original os)

edit : lol i was censured

Edited August 14, 2010 by malez

[Guest thenext1]

Be carrefull with root ! don't use any superboot, it a big s*** when not specially designed for your bin (Yes I know usally I speak in a correct way, but so many user contact me to tell me "my phone does not boot since i have installed a superboot" that i insist.)

Install malez recovery and use it to root your phone (if you still want to stay on original os)

edit : lol i was censured

Sure I did install your recovery and use the first rooting method.

Now it says it's rooted but I've yet to adb shell & rm it.

edit: I REALLY hope the sms problem has to do with the low space, coz It's still complaining with a simcard icon and the same message "text message memory full", like sms are stored on the sim like the old Motorola days. But then the sim message manager, in the SMS options, says the sim is empty...

Edited August 14, 2010 by thenext1

[Guest malez]

Sure I did install your recovery and use the first rooting method.

Now it says it's rooted but I've yet to adb shell & rm it.

edit: I REALLY hope the sms problem has to do with the low space, coz It's still complaining with a simcard icon and the same message "text message memory full", like sms are stored on the sim like the old Motorola days. But then the sim message manager, in the SMS options, says the sim is empty...

please install busybox with the recovery and give me this

adb shell df

adb shell du -s /data/*

I don't remember of seeing this message but i never stay a long time on an original bin. Just the time to fix bugs and enhance to provide a rom :D

Edited August 14, 2010 by malez

[Guest thenext1]

please install busybox with the recovery and give me this

adb shell df

adb shell du -s /data/*

I don't remember of seeing this message but i never stay a long time on an original bin. Just the time to fix bugs and enhance to provide a rom :D

Unfortunately I read this after having done the "rm" command. (And being back to 112MB free memory!! Thank you!)

anyway, df reports the following:

/dev: 95084K total, 0K used, 95084K available (block size 4096)

/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)

/system: 131072K total, 116688K used, 14384K available (block size 4096)

/data: 197376K total, 82324K used, 115052K available (block size 4096)

/cache: 91520K total, 1364K used, 90156K available (block size 4096)

/data/DxDrm/fuse: Permission denied

/sdcard: 1928992K total, 1178400K used, 750592K available (block size 32768)

[Guest gi4257]

Or just install the patch for 1.100.39 available on acer mobile website.

I've try to run this patch under my liquid and it does not work because there is a test to check that the device is not an A1 one. Should I force to run it by erasing the test ?How have you done to update your liquid with this patch ?

I found this assert in update-script and updater-script in the update.zip file

assert(getprop("ro.product.device") == "a1" || getprop("ro.build.product") == "a1");

[Guest eumate]

I've try to run this patch under my liquid and it does not work because there is a test to check that the device is not an A1 one. Should I force to run it by erasing the test ?How have you done to update your liquid with this patch ?

I found this assert in update-script and updater-script in the update.zip file

assert(getprop("ro.product.device") == "a1" || getprop("ro.build.product") == "a1");

have you tried from malez recovery or following the procedure contained in the zip?

I had to modify the update.zip to successuly flash in malez recovery, but should work on default recovery.

[Guest gi4257]

have you tried from malez recovery or following the procedure contained in the zip?

I had to modify the update.zip to successuly flash in malez recovery, but should work on default recovery.

I tried both and it did not work. I also try to delete the assert in the script-update and script-updater files but I got another error. Can you tell me exactly what you modified to make it works on a Liquid ? Thanks