ANDROID 2.1 T-MO UK UPDATE

[Guest mr.a]

heres a couple of screenshots or the people that wanted it

[Guest david_dawkins]

I am currently running the December update and I've never modded my Pulse in any way. Should I install this update?

Apply same reasoning that made you update in December; it's an official update from T-Mo.

I just upgraded from MCR 1.7, btw.

[Guest mr.a]

the files didn't get copied which will be due to running out of space on the system partition. Are you trying to add a2sd to the UK 2.1 rom?

thanks, just deleted a couple of apps from the system partition and it installed fine

btw how do i move google maps to data partition?

[Guest Totyasrác]

heres a couple of screenshots or the people that wanted it

I thought it had newer kernel... I mean... I dunno... :)

[Guest flip360]

can we have this rooted with a2sd as a flashable update .zip?

[Guest Cazomino05]

heres a couple of screenshots or the people that wanted it

THEMES?

Edited August 6, 2010 by Cazomino05

[Guest david_dawkins]

I thought it had newer kernel... I mean... I dunno... :)

It's newer than 1.5's 2.6.27, and is the standard release for 2.1.

[Guest mr.a]

can we have this rooted with a2sd as a flashable update .zip?

+1 i think flib is doing it already

[Guest DanWilson]

Where the Swype from? I thought it didn't work with the Pulse, and had expired. Will it come out on the market? I WANT IT!!!

[Guest Rem1x]

THEMES?

Tried, killed the install.

[Guest flip360]

+1 i think flib is doing it already

here also :)

[Guest mr.a]

Where the Swype from? I thought it didn't work with the Pulse, and had expired. Will it come out on the market? I WANT IT!!!

PM :)

[Guest Simon O]

Ok WTF, I think this update has changed the partition sizes again.

Output when I was on Hungarian 2.1:

# cat /proc/mtd

cat /proc/mtd

dev:	size   erasesize  name

mtd0: 00280000 00020000 "boot"

mtd1: 06e00000 00020000 "system"

mtd2: 05040000 00020000 "userdata"

mtd3: 01400000 00020000 "cache"

mtd4: 004c0000 00020000 "recovery"

mtd5: 00080000 00020000 "misc"

# mount

mount

rootfs on / type rootfs (ro)

tmpfs on /dev type tmpfs (rw,mode=755)

devpts on /dev/pts type devpts (rw,mode=600)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)

/dev/block/mtdblock1 on /system type yaffs2 (rw)

/dev/block/mtdblock2 on /data type yaffs2 (rw,nosuid,nodev)

/dev/block/mtdblock3 on /cache type yaffs2 (rw,nosuid,nodev)

/dev/block/mmcblk0p2 on /system/sd type ext2 (rw,noatime,nodiratime,errors=continue)

hwvefs on /data/hwvefs type fuse.hwvefs (rw,nosuid,nodev,user_id=0,group_id=0,allow_other)

/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0000,dmask=0000,allow

utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8)[/code]




Output on UK 2.1

[code]cat /proc/mtd

dev:	size   erasesize  name

mtd0: 00280000 00020000 "boot"

mtd1: 06400000 00020000 "system"

mtd2: 05a40000 00020000 "userdata"

mtd3: 01400000 00020000 "cache"

mtd4: 004c0000 00020000 "recovery"

mtd5: 00080000 00020000 "misc"

# mount

mount

rootfs on / type rootfs (ro)

tmpfs on /dev type tmpfs (rw,mode=755)

devpts on /dev/pts type devpts (rw,mode=600)

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)

/dev/block/mtdblock1 on /system type yaffs2 (ro)

/dev/block/mtdblock2 on /data type yaffs2 (rw,nosuid,nodev)

/dev/block/mtdblock3 on /cache type yaffs2 (rw,nosuid,nodev)

/dev/block/mmcblk0p2 on /system/sd type ext2 (rw,noatime,nodiratime,errors=continue)

hwvefs on /data/hwvefs type fuse.hwvefs (rw,nosuid,nodev,user_id=0,group_id=0,allow_other)

System is smaller, data is bigger :)

that would explain why my Nandroid backup didn't work...

Update:

/system is now 100MB

/data is now 90MB

Edited August 6, 2010 by flibblesan

[Guest Simon O]

Android 2.1 UK T-Mobile

Rooted, Superuser 2.2.2, Darktremor A2SD 2.7.5 rc1

Download: r1-update-pulse-uk-signed.zip - mirror

Known issue:

Force close on first boot. Click wait, and give it a minute before continuing setup.

[Guest Swiftes]

Android 2.1 UK T-Mobile

Rooted, Superuser 2.2.2, Darktremor A2SD 2.7.5 rc1

Download: r1-update-pulse-uk-signed.zip - mirror

Known issue:

Force close on first boot. Click wait, and give it a minute before continuing setup.

Installing now :)

[Guest flip360]

thanks flibble :)

[Guest Simon O]

thanks flibble :)

Well it was worth messing up my phone for a few hours :D

[Guest irvine]

Cheers flib! :D

Finally the UK ROM, but I keep on wondering if T-Mo NL will ever release an official 2.1 ROM... not betting my money on it :)

[Guest igor_anta]

Flibble can you refresh my memory :) What line do I change and where to keep Launcher in memory? Thanks.

[Guest rikkiej]

Flibble can you refresh my memory What line do I change and where to keep Launcher in memory? Thanks.

Launcherpro has it as a setting, look it up :)

[Guest igor_anta]

Launcherpro has it as a setting, look it up :D

ADW as well, but I wanted to do it the old fashion way, dabble in system files :D I think it was a local.prop that needed editing, but not sure :)

[Guest Simon O]

ADW as well, but I wanted to do it the old fashion way, dabble in system files :D I think it was a local.prop that needed editing, but not sure :)

It's around somewhere but I added the tweak to the kernel image in my rooted rom :D

[Guest rikkiej]

Anyone tried flashing a framework on the r1 rooted UK ROM? Does it work?

[Guest igor_anta]

It's around somewhere but I added the tweak to the kernel image in my rooted rom :D

Found it "Try setting "ro.HOME_APP_ADJ=1" at the end of /data/local.prop". Can find that in the rom .zip, is it missing in the newer release or do I have to do it after flashing the rom, darn it :)

[Guest DanWilson]

Found it "Try setting "ro.HOME_APP_ADJ=1" at the end of /data/local.prop". Can find that in the rom .zip, is it missing in the newer release or do I have to do it after flashing the rom, darn it :)

Isn't it one of the things that get built on first boot after flash (or whilst flashing)?