Help SMS memory full on a high end phone, lol? :)

[Fking]

Ok i missed coupe of SMS already because of "Full memory".
I've got nexus one with 8GB storage, but ocasionally my phone memory is full for a while, when i try a lot of new apps. And before move them to the SD card or uninstall.

If i get SMS during that period, it gots rejected because of "SMS memory full" and even after i free some space, it still doesn't get delivered, but obviosly lost for good.

So, isn't it funny, $500 phone, with hundreds of MBs internal memory and 8GB storage cannot get a simple few bytes SMS because of full memory. :>


p.s.
Is there a way around that?
I'm with 2.2 cyanogen

 

[rowuncw]

Maybe a stupid question, but is there a setting that allows you to change how much space is allocated to SMS messages?

 

[Knewz]

i believe the minimum amount of space required is 15mb. Anything lower and the phone may not receive text or emails.

 

[Teknologic]

It already starts at below 20 for me. And yeah, I was pretty dumbstruck when I first realized this as well. Especially because of how small an sms is, even compared to the smallest app. And because the system already reserves like 50 of our 250 megabyte internal mem.
And I'm still baffled as to why texts just get discarded then, instead of queued like when the phone is off or in airplane mode.
I haven't seen any mention of a fix for this. As a matter of fact, I haven't seen this problem mentioned much at all ever...

 

[Rusty]

As a matter of fact, I haven't seen this problem mentioned much at all ever...

Star this: Issue 4991 - android - Can not receive SMS when internal memory is low. - Project Hosting on Google Code

 

[Teknologic]

As always, right on the ball there rusty! I had already starred it way back but I didn't notice they FINALLY assigned someone to the problem less then a month ago. A bit late for an issue that had been open since 2009 and causes you to lose data. But it seems as a resolution to the issue is finally in sight.
By the way rusty, props to you. When I get around to responding to a topic, you've usually already responded faster and more adequate then I even could. You're practically holding this forum up by yourself at times
Good game sir, I know many people greatly appreciate it!

Edit: I read on and supposedly this issue has gotten a quick fix in gingerbread already. It should then only occur at less then 1mb internal storage (which should never happen). So that's enough reason for me to actually look forward to gingerbread again. And probably get back to flashing roms

 

[Fking]

Thanks, its good to know that at least they are aware and will be fixed.
I also was feeling like nobody is talking about that, and it could be serious issue.

In the meantime i'll keep my free memory high :>

 

[jjparks]

Seems to be resolved here
.

I have HTC desire and am following this:

Comment 50 by teej...@gmail.com, Oct 12, 2010
It might help to understand the reason behind this issue.

Linux typically reserves a fixed % of a block device for use only by root so that if the device runs out of space for regular users the root user (and privileged system processes) can still write to the device. If I recall correctly the reserved amount is 5%.

I encountered this issue recently on an HTC Desire with Cyanogenmod 6.0.2 (Android 2.2 Froyo).

Symptoms were:

1. Seeing the "Low storage space" warning
2. Unable to receive new emails using the Gmail app
3. Downloads inexplicably failing to start in the Market

I found this issue report and from it discovered the reason and a fix.

Reason:

The device has a fixed amount of EEPROM (electrically erasable programmable read only memory) aka 'flash memory' that you can think of as equivalent to a hard disk - it stores programs and data when the device has no power.

On the HTC Desire there is 512 Megabytes of EEPROM (aka ROM).

Android partitions this storage space into three block devices, each with it's own file-system. They are 'system' (the operating system files and libraries), 'cache' (temporary files created and used by running processes) and 'user' (databases and other files created by all the applications on the device).

By default the EEPROM space is divided in a way that leaves lots of unusable free space. On the HTC Desire there was ~120MB free in 'system' and ~30MB free in 'cache'.

The 'user' partition is the one that is running low on free space. On the Desire it had less than 6MB free which is inside the 5% limit mentioned, meaning regular apps that don't run with root privileges couldn't write more data.

In addition, the dalvik virtual machine's cache (where the native executable code to run each app is stored) is also stored in the 'user' partition. This means that the more apps that are installed and run the more space in 'user' is in use.

Some determined hackers discovered a way to change the sizes of these partitions so that the 'system' and 'cache' partitions can be shrunk to be just slighter larger than is needed ('system' only needs to be large enough for the Android system files and any apps bundled with the phone such as the Google Apps).

After following the guides on how to change the partition sizes my HTC Desire went from ~6MB to 170MB free in 'user'.

The instructions for the G1 are at:

1. Back-up, resize the partitions, restore, reboot. [MOD][RECOVERY] Firerat's Custom MTD Partitions (resize Data,System and Cache) - xda-developers

The HTC Desire requires an additional step to 'unlock' the EEPROM since HTC have included the @secuflag stored in the radio's NVRAM which forces 'system' to be read-only, preventing the re-partitioning.

So, for HTC Desire it's:
1. Replace HBoot loader with one that ignores the @secuflag.
[AlphaRev] HBOOT S-OFF Desire GSM 1.8 - xda-developers
2. Back-up, resize the partitions, restore, reboot. [DEV][S-OFF] Custom MTD Partitions (resize data, system, and cache) - xda-developers