Partition sizes and memory

[Guest rjm2k]

Am I correct in assuming that the increased partition sizes in 2.1 is what's reducing the amount of free memory? If so, would it be worth using the 1.5 partition sizes with a trimmed down 2.1 so that we end up with more available memory?

Also, would custom partition sizes be even better? We now have 2 or 3 updata's that change the partition size, assuming it's the same bit of code doing the change in each update, then each instance should be pretty much the same but with a slightly different table for the partition sizes, maybe that means someone can spot the code and workout how to manipulate the table? Or at lease, maybe someone could extract the 1.5 (or timemachine) partition manipulation code to allow us to use smaller partitions for 2.1?

[Guest DanWilson]

Am I correct in assuming that the increased partition sizes in 2.1 is what's reducing the amount of free memory? If so, would it be worth using the 1.5 partition sizes with a trimmed down 2.1 so that we end up with more available memory?

Also, would custom partition sizes be even better? We now have 2 or 3 updata's that change the partition size, assuming it's the same bit of code doing the change in each update, then each instance should be pretty much the same but with a slightly different table for the partition sizes, maybe that means someone can spot the code and workout how to manipulate the table? Or at lease, maybe someone could extract the 1.5 (or timemachine) partition manipulation code to allow us to use smaller partitions for 2.1?

We can't change the UPDATA.APP's, but we do have a trimmed down 2.1, although it was so unreliable, it was unreal.

And the things that couldn't fit on the system partition where moved to the data partition. You don't really win.

I did suggest custom partition sizes, although it was ignored. I'm totally sure that it'd work, just I don't know how to do it (I suggested a data partition of almost 0, and the system partition gets the rest - for A2SD people)

I know for fact however that we'd need to fastboot flash it.

[Guest Speckles]

We can most likely alter the partition sizes (not that difficult as its standard nand) but altering them on a running system is not a good idea so really needs to be done from recovery.

It's far easier to use Apps2SD and the original HU partition sizes which give more space to the system partition.

[Guest de_shepherd]

Aren't there 2 different issues at work here?

1) Flash size is not big enough (especially after 2.1 increased in size compared to 1.5) so there's not much space to store apps + their saved data.

2) RAM isn't big enough either (again 2.1 may take more space?) which means apps get suspended or killed if there's any significant multitasking

While 1) can be addressed by a2sd etc 2) is, I think, inherent in the Pulse having less RAM than newer phones designed for 2.1 - can possibly be partially allieviated by the attempts to discover which services etc can be prevented from running

[Guest Speckles]

Yes, there are the two which you state. The Pulse was always meant as a budget 'entry level' phone.

The only real solution is to upgrade to a newer model. I've just bought a Galaxy S which has 8GB flash and 512MB RAM, so I'm expecting it to fly. I'm then going to use my Pulse for development work, as I no longer need it as a phone (eg. the OS doesn't work properly, you try to figure out why, and a call comes in). Of course then when you go back to your stable OS after your dev work, you loose your call logs, text's, etc.

[Guest Simon O]

Yes, there are the two which you state. The Pulse was always meant as a budget 'entry level' phone.

The only real solution is to upgrade to a newer model. I've just bought a Galaxy S which has 8GB flash and 512MB RAM, so I'm expecting it to fly. I'm then going to use my Pulse for development work, as I no longer need it as a phone (eg. the OS doesn't work properly, you try to figure out why, and a call comes in). Of course then when you go back to your stable OS after your dev work, you loose your call logs, text's, etc.

Galaxy S is a niiiiiiiiiiiiiiiice phone. The Android 2.2 ROM will be out by the end of September :)

[Guest Tom G]

We can most likely alter the partition sizes (not that difficult as its standard nand) but altering them on a running system is not a good idea so really needs to be done from recovery.

I have a modified recovery image that adds an extra mtd device (mtd6) which is the entire nand (including areas not mapped to a partition). If anyone wants it let me know.

I don't know how the partition layout is controlled, but from the brief look I have had at nand dumps I couldn't see anything there that sets the structure. The kernel source should show how it determines where each partition is and should give some ideas how to change them.