[ROM][Eclair] Avalanche v1 [2011-01-07] [OLED+TFT]

[Guest isambard]

What is it?

- Based on Seb's r7 2.1 ROM for stability.

- Repartitioned to give 320mb of data space

- Default launcher replaced with Launcher pro

This is first release and just for testing. I'm not sure if the extremely small system size is going to cause problems. Or particularly the removal of core items like launcher.

This release is recommended only for testers.

md5sum 103b8237db162530f6d9a6616a629875 avalanche1.zip

Filesystem                Size      Used Available Use% Mounted on

tmpfs                   207.4M     12.0K    207.4M   0% /dev

/dev/block/mtdblock5     96.0M     91.4M      4.6M  95% /system

/dev/block/mtdblock6    319.6M     25.7M    293.9M   8% /data


APPs installed


com.android.settings.apk

com.fede.launcher-1.apk

com.android.phone.apk

com.android.vending.apk

com.android.contacts.apk

com.android.mms.apk

com.android.camera.apk

com.cooliris.media.apk

com.android.browser.apk

com.google.android.talk.apk

com.android.music.apk

com.android.calendar.apk

com.android.inputmethod.latin.apk

com.google.android.googleapps.apk

com.google.android.apps.gtalkservice.apk

com.android.bluetooth.apk

com.google.android.apps.uploader.apk

com.zte.smartdialer.apk

com.google.android.providers.enhancedgooglesearch.apk

com.android.providers.subscribedfeeds.apk

com.noshufou.android.su.apk

com.android.providers.calendar.apk

com.android.providers.contacts.apk

com.android.soundrecorder.apk

com.android.globalsearch.apk

com.android.packageinstaller.apk

com.android.providers.downloads.apk

com.android.providers.telephony.apk

com.android.certinstaller.apk

com.android.googlesearch.apk

com.google.android.providers.settings.apk

com.google.android.location.apk

com.android.providers.media.apk

com.google.android.providers.talk.apk

com.google.android.providers.subscribedfeeds.apk

com.google.android.syncadapters.contacts.apk

com.google.android.server.checkin.apk

com.android.providers.settings.apk

com.google.android.partnersetup.apk

com.irdeto.providers.drm.apk

android.tts.apk

com.android.server.vpn.apk

com.android.qualcomm.apk

com.android.providers.drm.apk

com.android.providers.applications.apk

com.android.htmlviewer.apk

com.android.vending.updater.apk

com.android.providers.userdictionary.apk

com.svox.pico.apk[/codebox]

Can any more fat be trimmed?

EDIT: whoops. not deleting setupaccount.apk might have been helpful :unsure: testers, i'm afraid you'll have to adb push this back on.

EDIT: i think i really pushed the size too far. not really usable so i'm going to repartition and try again. link deleted until next release ready.

Edited January 7, 2011 by isambard

[Guest Rotmann]

Hehe, love the names you give to your ROMs. I don't really think the interest for 2.1 will be that big anymore now with the kernel source for Froyo available. Good luck though!

Edit: what happened to the Volcano?

volcano 0.3

url removed pending further testing.

Edited January 7, 2011 by Rotmann

[Guest wbaw]

I think 128mb is small enough for system, it allows some headroom so we can install other roms. Have you tried moving the cache to /data & removing or resizing the cache partition?

[Guest isambard]

Hehe, love the names you give to your ROMs. I don't really think the interest for 2.1 will be that big anymore now with the kernel source for Froyo available. Good luck though!

Edit: what happened to the Volcano?

volcano 0.3

url removed pending further testing.

well, currently, i put both my Blades out of action due to 'experiments' so I'm back to my nokia E71 for now. the idea for Avalanche was to go back to a good stable workhorse ROM so i can use one of my blades as a phone and then i can go back to experimenting on the second blade with the 'unstable' mods.

[Guest isambard]

I think 128mb is small enough for system, it allows some headroom so we can install other roms. Have you tried moving the cache to /data & removing or resizing the cache partition?

there shouldn't be a problem with resizing the cache partition. there was some talk of this on the partitioning thread, but i haven't developed it further as i've seen no issues with the current size of the cache partition.

[Guest IronDoc]

EDIT: i think i really pushed the size too far. not really usable so i'm going to repartition and try again. link deleted until next release ready.

What happened? Was it throwing out errors because of the small size or what?

[Guest isambard]

What happened? Was it throwing out errors because of the small size or what?

it was 3am when i was working on it and at the time i was pressing the power button without the battery in and wondering why it wouldn't power on. i'm going to take a look at it again this w/e and make sure it's good before inflicting it on others :unsure:

[Guest wbaw]

there shouldn't be a problem with resizing the cache partition. there was some talk of this on the partitioning thread, but i haven't developed it further as i've seen no issues with the current size of the cache partition.

The cache partition is another 40mb, of which about 3 or 4 seems to get used on my phone, so it's some more wasted space that could be used for apps on the data partition. If I knew how to edit the partitions on the phone, I'd have a go myself. Ideally move the cache to /data, symlink it or something.

[Guest oh!dougal]

there shouldn't be a problem with resizing the cache partition. there was some talk of this on the partitioning thread, but i haven't developed it further as i've seen no issues with the current size of the cache partition.

What size are you are currently using? (Not mentioned in post 1)

IF it is possible to redirect /cache to mount /data/cache in its stead, then there would be no (practical) external constraint on its size, while not wasting any freespace (most of the space) in /cache.

I would expect that SoundRecorder and Music were also trimmable fat (unless specified as default apps for handling specific file types, or providing standard methods used by alternates?) Market has better (free) alternatives.

Have you pruned out the "musical" ringtones and alerts? Seems to me that people that are keen on such things want their own!

I tend to agree that a sensible target looks like /system being comfortable at 128mb.

If that were adopted as a "standard re-partitioning" then different folks could be making their "skinny" roms to suit, rather than expecting constant re-partitioning. 128 should leave enough room for goodies like plural keyboards. The Blade shouldn't need a Lenten sacrifice of useful stuff.

For most of us, 128 for /system means that /data is plenty big enough not to be bothering with shunting things to the sdcard.