yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile General] lmen91:
Well Tmobile is cheaper and faster 3G, depends on your area how well your reception might be. Around where I live ATT has a much better reception than Tmobile. I think it comes down to that, you get what you pay for. The phones are going to do the same thing..I got my touchpro 2 for tmobile for 229.99 upgrading through wirefly, they'll sell it to you for 199.99 if you are a new customer and get the data plan which you need either way.
[Touch Pro2, Tilt 2 Windows Mobile General] solsearch:
like lmen said. The phone is going to be capable of the exact same things, except for using different 3G bands (and the slight slim chance the AT&T version will have a 3.5mm jack).

The best way to decide is to see who has the best coverage in the areas you will need it and compare the plans that that suit you. Sometimes the plans can vary greatly. Did you see the article where US, Canada and I think Australia are the most expensive countries for cell phone usage?
[Touch Pro2, Tilt 2 Windows Mobile General] michael60617:
yea tmobile is alot cheaper....for me right now i pay about 110 a month i have 900 mins with rollover and pda+ messaging but with tmobile i can drop the price to 84 with the my fave 600mins i dunno i have to see how reception is because i dont have any call problems now im using the tilt....all of this is coming cause i want the tp2 so bad lol
[Touch Pro2, Tilt 2 Windows Mobile General] buttsbuttsbutts:
I've had great luck with Tmo's 3G and my TP2/G1
[Touch Pro2, Tilt 2 Windows Mobile General] HeavyComponent:
One of the biggest mistake is to never leave your carrier because of one phone! But since your contract is up then I guess it's ok!!!
[Touch Pro2, Tilt 2 Windows Mobile General] solsearch:
:eek:

Sorry, I always find it preposterous how much people pay for cell phones in the US and Canada. I pay between 8 and 13 dollars US a month (no data included though, but then again, I have wifi at home at the university and some hotspots around the city thanks to my home ISP).

the carriers really need to stop gouging customers.
[Hero, G2 Touch Q&A, Help & Troubleshooting] kazlan:
Hi,

did anyone find a way to remove the words that IME automatically adds to the dictionary? in case you add some garbage by mistake.
[Hero, G2 Touch Q&A, Help & Troubleshooting] kazlan:
update

found a file in /data/data/com.htc.htcime called udb which seems to have the words in it but it's in a format I dont see how to edit.
[Hero, G2 Touch Q&A, Help & Troubleshooting] cdmackay:
mmm, my /data dir seems to be empty? At least, various file mgrs claim so. Can't check from the cmdline owing to ConnectBot kbd bug.
[Hero, G2 Touch Q&A, Help & Troubleshooting] kazlan:
yep, think you need root to see the folder's content.

anyway, deleting that folder cleared the keyboard "word cache". Not the best way but it worked.
[Hero, G2 Touch Q&A, Help & Troubleshooting] cdmackay:
thanks; good info.

I read that getting root disabled the ability to download paid apps from Market; is that true?
[Hero, G2 Touch Q&A, Help & Troubleshooting] kazlan:
Not on my Hero, just bought Tweetcat a few hours ago with no problem
[Hero, G2 Touch Q&A, Help & Troubleshooting] cdmackay:
marvelous! thanks, I wanted to get root to use nandroid backup, but was worried; any other downsides to getting root?

[apols for dragging this off-topic, too]
[myTouch 3G, Magic Android Development] biktor_gj:
First of all, this is not another lame post about why vodafone's magic has less ram than htc one. This is just... another thing about partly the same issues.

Second, this is also not about rosie. If you're going to say if this will make rosie work better, don't post. I really don't give a **** about rosie. I'm just trying to get more of this hardware.

Now for the topic. As you will already know, there are two variants of the Sapphire. One, supposedly has 192 Mb of RAM (Vodafone) and the other one has 288 (HTC). So far OK.

BUT, Vodafone Magic kernel reports 98Mb of available RAM. Wait, what? Even if the radio firmware eats part of the memory (about 20mb on msm7200 SoC), the kernel should report more than half of the memory the ram ic supposedly has. Furthermore, looking at the kernel source I found this on the memory fixup code (wich I assume is where it reserves the baseband ram area, like on other phones):

mi->nr_banks = 1;
mi->bank[0].start = PHYS_OFFSET;
mi->bank[0].node = PHYS_TO_NID(PHYS_OFFSET);
if (smi_sz == 32) {
mi->bank[0].size = (84*1024*1024);
} else if (smi_sz == 64) {
mi->bank[0].size = (101*1024*1024);
} else {
printk(KERN_ERR "can not get smi size\n");

/*Give a default value when not get smi size*/
smi_sz = 64;
mi->bank[0].size = (101*1024*1024);
printk(KERN_ERR "use default : smisize=%d\n", smi_sz);
}

As I stated before, qualcomm phones seem to use part of the ram for the baseband firmware, and, at least on Kaiser and Nikes (wich are the ones I know better, at least on the code side), have splitted the ram banks so the kernel doesn't try to write to the baseband memory corrupting it all, for example, kaiser:

mi->nr_banks=2;
mi->bank[0].start = 0x10000000;
mi->bank[0].node = 0;
mi->bank[0].size = 0x03800000;
mi->bank[1].start = 0x14000000;
mi->bank[1].node = 0;
mi->bank[1].size = 0x02d00000;

But on the Magic, there's no splitting. If it detects smi_size=32 (htc, though it's not really working) it throws 101 mb of RAM. if it detects smi_size=64( vodafone), it throws 88 mb

I might be completely wrong, and maybe there's another routine that I haven't seen or something like that, but it feels to me like they ran out of time while coding it and they left the fixup so it did boot, but didn't bother debugging to get the maximum ram amount, so they coded the minimal and left the rest for the modem "just in case". I'm going to do a few tests, but if someone knows something I don't please feel free to enlighten me :)
[myTouch 3G, Magic Android Development] biktor_gj:
I was partially right :)

First test, first success :)

Before tricking:

/proc # cat meminfo

MemTotal: 97876 kB

MemFree: 3324 kB

Buffers: 384 kB

Cached: 22788 kB

SwapCached: 0 kB

Active: 37820 kB

Inactive: 40320 kB

Active(anon): 26548 kB

Inactive(anon): 29000 kB

Active(file): 11272 kB

Inactive(file): 11320 kB

Unevictable: 256 kB

Mlocked: 0 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 55248 kB

Mapped: 13360 kB

Slab: 6592 kB

SReclaimable: 1136 kB

SUnreclaim: 5456 kB

PageTables: 5108 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 48936 kB

Committed_AS: 1487028 kB

VmallocTotal: 155648 kB

VmallocUsed: 70820 kB

VmallocChunk: 33788 kB

After first attempt:

MemTotal: 102004 kB

MemFree: 4420 kB

Buffers: 2384 kB

Cached: 51580 kB

SwapCached: 0 kB

Active: 53508 kB

Inactive: 33744 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 33312 kB

EDIT: Okay, definitely, we can get more free ram than what it's actually available. After a few test, I'm getting 106mb of total RAM. This is only tricking the first memory bank, without telling the kernel there's a hole (wich by the way there is as I have already trashed it twice :)) in the middle of the memory space. More proof:

Fourth attempt:

# cat proc/meminfo

MemTotal: 106068 kB

MemFree: 25916 kB

Buffers: 20 kB

Cached: 45920 kB

SwapCached: 0 kB

Active: 41660 kB

Inactive: 30048 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 25812 kB

Mapped: 21176 kB

Slab: 3596 kB

SReclaimable: 964 kB

SUnreclaim: 2632 kB

PageTables: 2528 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 53032 kB

Committed_AS: 693744 kB

VmallocTotal: 147456 kB

VmallocUsed: 61148 kB

VmallocChunk: 65532 kB

Regards!
[myTouch 3G, Magic Android Development] Amon_RA:
Impressive!

:eek: 32B owners : prepare yourself for a whole new experience ;)

Could this be related to the fact that 32A kernels are not working on a 32B radio?
[myTouch 3G, Magic Android Development] biktor_gj:
I think so, yes. As memory sizes are different, memory addresses change, that could be one of the reasons why 32a and 32b kernels aren't compatible between devices. Though I don't know if there'll be something else I don't know (wich probably there is).

So far, I found that on the beginning of the memory space, I can get up to 108 Mb of RAM without corruption (or reboots, or strange things) on my 32B magic. I have splitted the memory in two banks on the code, and trying to get some more free space at the end of the memory, but with no luck yet (working on this for an hour or two, I don't expect to be THAT fast ;) )

But, it's a quite nice start. Even if we can't get the full 192 mb (wich we can't because of the radio), maybe we can get up to 150 or 160Mb, wich would be quite better than what we have. What I have to find is where the radio memory ends so I don't screw it, and then get to the last writable address. Trial and error :)
[myTouch 3G, Magic Android Development] bcrook:
Do you mean that this may help track down why when 32a owners flash the 32b radio we lose all of our RAM?
[myTouch 3G, Magic Android Development] mr.r9:
Good luck man! I wish I can help with this technical stuff :D
[myTouch 3G, Magic Android Development] wire103:
Hmm, perhaps not quite. Your approach seems a bit "unscientific". You might get the impression that you're not overwriting anything, but what if some seldom used part of the memory is overwritten. You might not notice until the baseband gets in a special situation.

(Sorry, "unscientific" sounds rude, but it's not meant that way. I think you're making great progress!)

Is it possible to map part of the memory as read-only?

If that is the case, couldn't we build a test kernel that maps 64mb of the first memory as accessible, and the rest as readonly. Then do a custom recovery initrd that just dumps all memory to the PC and analyse the layout there?
[myTouch 3G, Magic Android Development] hakeem9:
I would be willing to test this on my 32A if you want to put something together. It would be superb if we could get 32B ROM's working on the 32A using the full available RAM, or even more available RAM than a default 32A ROM.

PM me if you want to use me as a mule.
[myTouch 3G, Magic Android Development] magpie2000k:
This looks very interesting the outcome could be of huge benefit to all.

Just wish I could add some tech knowledge but I cant.

Will continue to read with interest well done great work so far
[myTouch 3G, Magic Android Development] hakeem9:
EDIT: nm, it is in the kernel source.
[myTouch 3G, Magic Android Development] biktor_gj:
I can try something for 32A users, if you don't mind risking your phone.,.

Let's see if I get it right.

Given a 32A board, can you pick a 32b boot.img, radio and rom, flash it, and boot all the way to the home screen, and the only thing you'd loose is the upper memory? (making the phone think it has 100mb of ram)?

If that's the case, and 32b kernels CAN boot on 32A boards given the right Radio version, it's a matter of patching the memory bank sizes so the kernel knows it has more ram than what it's declared...
[myTouch 3G, Magic Android Development] hakeem9:
That's exactly right. Using a 32B radio I can boot any 32B ROM but am down 100mb. If you can compile a 32B kernel for me that uses more RAM I will try it out.

For reference, here is what my meminfo looks like currently:

MemTotal: 197144 kB

MemFree: 15380 kB

Buffers: 264 kB

Cached: 36244 kB

SwapCached: 0 kB

Active: 104564 kB

Inactive: 18568 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 86648 kB

Mapped: 17496 kB

Slab: 48268 kB

SReclaimable: 41132 kB

SUnreclaim: 7136 kB

PageTables: 6244 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 98572 kB

Committed_AS: 1669088 kB

VmallocTotal: 319488 kB

VmallocUsed: 65884 kB

VmallocChunk: 201724 kB
[myTouch 3G, Magic Android Development] Killadude:
Aweome if it works...

1 Lab Rat signing up for 32A!
[myTouch 3G, Magic Android Development] biktor_gj:
There's a value that seems to change between boards. That's the SMI size. On 32B boards its value is 64, and on 32A boards is 32. Can you flash it all with 32b rom and radio, and post some info elsewhere?

What I need is the kernel messages log. You can get it by getting a root shell (adb shell), and running the command:

dmesg > /sdcard/dmesg.txt

Then uploading that file somewhere to pick up (the easiest, pastebin.com)

I need to see if even if it's running a 32b kernel, it detects the correct smi size, or if it picks the generic one. If it detects the correct size, we may have a chance of autodetecting the board revision on boot.
[myTouch 3G, Magic Android Development] hakeem9:
Doing it now, standby
[myTouch 3G, Magic Android Development] Killadude:
so you want some one with a 32A to flash a 32B rom and then get the dmesg? or the origanal 32A?
[myTouch 3G, Magic Android Development] biktor_gj:
I need the 32B kernel dmesg when running on a 32A board :)

Sorry for my english... ;)
[myTouch 3G, Magic Android Development] hakeem9:
Ok, attached is dmesg-32A and dmesg-32B.

dmesg-32A is using a 32A ROM (from Amon_RA) and dmesg-32B is using cyanogens 3.9.7 (32B) ROM, both running on my Rogers 32A.

http://www.mediafire.com/?sharekey=87a195e0707967d00f83d91f6dff7c385048c6f0b06623c55621d66e282a0ee8

Resultant meminfo:

MemTotal: 80724 kB

MemFree: 1356 kB

Buffers: 316 kB

Cached: 24352 kB

SwapCached: 0 kB

Active: 30156 kB

Inactive: 38332 kB

Active(anon): 21284 kB

Inactive(anon): 23068 kB

Active(file): 8872 kB

Inactive(file): 15264 kB

Unevictable: 248 kB

Mlocked: 0 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 44080 kB

Mapped: 14460 kB

Slab: 5244 kB

SReclaimable: 812 kB

SUnreclaim: 4432 kB

PageTables: 2808 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 40360 kB

Committed_AS: 727200 kB

VmallocTotal: 172032 kB

VmallocUsed: 44404 kB

VmallocChunk: 82940 kB
[myTouch 3G, Magic Android Development] biktor_gj:
hmmm... cool! it detects the SMI Size!

If this works, you will have about 150 or 160 mb of ram and no wifi :) (but the wifi thing is because of the wlan.ko)

Let's see what it does!

http://rapidshare.com/files/267026365/bootnew.img

do a fastboot boot bootnew.img, don't even bother flashing for now

If it doesn't work, it will either get stucked, or show the bootlogo, and after a while, it will reboot, then start booting the firmware stored on flash, but it won't break anything.

If it boots all the way, get a shell and do a

cat /proc/meminfo to see how much ram you get, or take a look at the dmesg
[myTouch 3G, Magic Android Development] Killadude:
testing now....

EDIT Nope dosent go past the first splash....

EDIT 2 Am trying again maybe i did something wrong while flashing 32b radio
[myTouch 3G, Magic Android Development] Gonzz:
what does the logcat show ?
[myTouch 3G, Magic Android Development] Killadude:
nothing it said waiting for device... was just stuck am tying again will have results in 2 min

EDIT SAME RESULT!

the normal 23b image rums normally but when trying this one it fails!
[myTouch 3G, Magic Android Development] redmdc:
hmm

just so i get what your trying to conker here. are you infact trying to say that 32b has the same mem as the 32a and its just locked up somewhere or are you gaining more memory by opening it up more with allowing us to use these 'holes'?

i have been following this progress and wouldnt mind finding out and maybe having some input into this :)
[myTouch 3G, Magic Android Development] magpie2000k:
the suspense is killing us excuse the pun
[myTouch 3G, Magic Android Development] biktor_gj:
Nope what I'm saying is that at least the 32B board has a little more RAM available for the userspace that what the kernel originaly estimates, and that with a patch to the google kernel source we can get compatible kernels for all boards but allowing the 32A revision get the memory it should have available, while running the 32B Radio (using the smi_sz parameter wich is autodetected on kernel init).

Now, for everyone else, it didn't have to worked, probably I have to reallocate the memory addresses more before making it work. The other approach is simply declaring a second bank with the remaining memory. Wich is what I'm going to try and drop a link when I have it finished :)

Regards
[myTouch 3G, Magic Android Development] hakeem9:
Trying this now, standby
[myTouch 3G, Magic Android Development] hakeem9:
Yup, same result. Doesn't get past the boot splash screen and waiting for device in adb.
[myTouch 3G, Magic Android Development] biktor_gj:
too many posts to edit and pretend somebody to see it...

I forgot to remove one thing, sorry. Deleted previous link, try this instead:

You should have, if running on 32b board:

MemTotal: 106068 kB

MemFree: 1888 kB

If you're running on 32A you should have slightly less

http://rapidshare.com/files/267044103/bootnew.img
[myTouch 3G, Magic Android Development] Killadude:
strange... this time it did boot but rebooted at the spashscreen!

in adb logcat it stopped at initializing graphics hw
[myTouch 3G, Magic Android Development] hakeem9:
Got just past the splash screen with my 32A and then the screen became garbled and the phone rebooted. I managed to get in a quick adb meminfo while that was happening which showed:

MemTotal: 102996 kB

MemFree: 62752 kB

Buffers: 28 kB

Cached: 26980 kB

SwapCached: 0 kB

Active: 12312 kB

Inactive: 23184 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 8500 kB

Mapped: 13328 kB

Slab: 2620 kB

SReclaimable: 748 kB

SUnreclaim: 1872 kB

PageTables: 768 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 51496 kB

Committed_AS: 84728 kB

VmallocTotal: 147456 kB

VmallocUsed: 37160 kB

VmallocChunk: 90108 kB
[myTouch 3G, Magic Android Development] wire103:
Hmm - I'm tinkering with my 32A, but this is new territory for me with embedded devices.

I took apart recovery-RAv1.2.0H.img with split_bootimg.pl just to test this out. The resulting kernel should be the 32A kernel, and booting this with fastboot does boot my phone.

Fastbooting the extracted kernel+initrd.gz hangs. Reassembling the two files with mkbootimg creates a file of same size as the original .img, but this also hangs on boot, but the original works (and is a bit different in the header content wise). What am I missing?

Ofcourse booting the kernel I compiled myself also hangs, but that is expected :-D

biktor_gj: Could I bother you for your .config file? Thanks!

Isn't the only viable way to get things going a serial cable on the ExtUSB port, so we can see whats going on?
[myTouch 3G, Magic Android Development] scargoll:
Hello,

With my 32B, it goes on loop at the splashscreen but i've well 106Mo of ram !!! :

adb shell cat /proc/meminfo

MemTotal: 106068 kB

MemFree: 16500 kB

Buffers: 12 kB

Cached: 75136 kB

SwapCached: 0 kB

Active: 55360 kB

Inactive: 27860 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 8096 kB

Mapped: 14800 kB

Slab: 4232 kB

SReclaimable: 1084 kB

SUnreclaim: 3148 kB

PageTables: 728 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 53032 kB

Committed_AS: 81344 kB

VmallocTotal: 147456 kB

VmallocUsed: 53952 kB

VmallocChunk: 65532 kB

Scargoll.
[myTouch 3G, Magic Android Development] hakeem9:
My 32A is standing by ready for testing. If this works, presumably we can just have cyanogen and others who are compiling custom kernels include your .c file during their process to end up with a perfect 32A port (using 32B radio).

Hurry up already :)
[myTouch 3G, Magic Android Development] ccyrowski:
I compile custom kernels/boot.img's for all of my ROMs. Just toss me the file and I'll make.
[myTouch 3G, Magic Android Development] Wysie:
If this works out we'll have 32A phones with 32B radios running 32B ROMs without "losing" RAM! Can't wait! :D
[myTouch 3G, Magic Android Development] biktor_gj:
This is just a different approach. It doesn't even have to work. I remapped some things so the kernel gets to think it has two different memory banks on the 32A, the first one more or less the way it originally was (with a little more RAM) and the otherone after the reserved memory block for console logging (wich by the way should be the last part to write besides the vmalloc region)

I also reduced the size limit for the 32B, for all the people who was seeing garbage on the screen and reboots (just in case).

http://rapidshare.com/files/267201449/bootnew.img (previous link deleted)

Let me know what you see!

Regards!
[myTouch 3G, Magic Android Development] Deicist:
this is on my 32b:

MemTotal: 104020 kB

MemFree: 62492 kB

Buffers: 16 kB

Cached: 31020 kB

SwapCached: 0 kB

Active: 24040 kB

Inactive: 12392 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 5420 kB

Mapped: 11024 kB

Slab: 3000 kB

SReclaimable: 812 kB

SUnreclaim: 2188 kB

PageTables: 708 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 52008 kB

Committed_AS: 79316 kB

VmallocTotal: 147456 kB

VmallocUsed: 53952 kB

VmallocChunk: 65532 kB

Hangs at black screen after splash screen.
[myTouch 3G, Magic Android Development] njakobs:
On 32b board

Normal Boot Image

MemTotal: 98328 kB

MemFree: 1956 kB

Buffers: 104 kB

Cached: 20920 kB

SwapCached: 3508 kB

Active: 39656 kB

Inactive: 42948 kB

Active(anon): 31152 kB

Inactive(anon): 31236 kB

Active(file): 8504 kB

Inactive(file): 11712 kB

Unevictable: 252 kB

Mlocked: 0 kB

SwapTotal: 30760 kB

SwapFree: 15848 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 59200 kB

Mapped: 15448 kB

Slab: 3796 kB

SReclaimable: 816 kB

SUnreclaim: 2980 kB

PageTables: 5164 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 79924 kB

Committed_AS: 1517416 kB

VmallocTotal: 155648 kB

VmallocUsed: 69812 kB

VmallocChunk: 23548 kB

with biktor_gj bootnew.img

cat /proc/meminfo

MemTotal: 104020 kB

MemFree: 55220 kB

Buffers: 16 kB

Cached: 33328 kB

SwapCached: 0 kB

Active: 27372 kB

Inactive: 16524 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 0 kB

Writeback: 0 kB

AnonPages: 10592 kB

Mapped: 16408 kB

Slab: 2772 kB

SReclaimable: 808 kB

SUnreclaim: 1964 kB

PageTables: 740 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 52008 kB

Committed_AS: 89580 kB

VmallocTotal: 147456 kB

VmallocUsed: 53952 kB

VmallocChunk: 65532 kB

Does not compelte boot and hangs

Cheers
[myTouch 3G, Magic Android Development] biktor_gj:
That's bothering me. I'm using one of yesterday's boot image, haven't rebooted the phone yet, and it's giving me 0 problems (besides wifi wich doesn't work). It needed a little longer to boot, but it ended up booting correctly. Are you all having this issue?
[myTouch 3G, Magic Android Development] scargoll:
Hello,

On my 32B, loop into splashscreen :

adb shell cat /proc/meminfo

MemTotal: 104020 kB

MemFree: 35584 kB

Buffers: 12 kB

Cached: 44648 kB

SwapCached: 0 kB

Active: 32872 kB

Inactive: 28568 kB

SwapTotal: 0 kB

SwapFree: 0 kB

Dirty: 196 kB

Writeback: 0 kB

AnonPages: 16804 kB

Mapped: 17932 kB

Slab: 4260 kB

SReclaimable: 888 kB

SUnreclaim: 3372 kB

PageTables: 1160 kB

NFS_Unstable: 0 kB

Bounce: 0 kB

WritebackTmp: 0 kB

CommitLimit: 52008 kB

Committed_AS: 246804 kB

VmallocTotal: 147456 kB

VmallocUsed: 54980 kB

VmallocChunk: 65532 kB

Scargoll.
[myTouch 3G, Magic Android Development] njakobs:
I tried again and left it sitting for ages and didn't complete the boot. I am using Deicist superlight hero rom at the moment not sure what effect that would have. Are you still using that rom to Deicist?
[myTouch 3G, Magic Android Development] Deicist:
Aye, still using my ROM.

It's a hero based rom, not sure if that makes any difference to how it boots :/