Fatal1ty made me think about the fact that the two versions of HTC Magic sold in Italy come with a different RAM amount:
adb shell cat /proc/meminfo gives these results:
Vodafone: about 98436 KB
TIM: about 192000KB
HOW COULD IT BE???
If it'll be confirmed, would it be legal to sell the same device with different characteristics without informing consumers?
asci said:
Fatal1ty made me think about the fact that the two versions of HTC Magic sold in Italy come with a different RAM amount:
adb shell cat /proc/meminfo gives these results:
Vodafone: about 98436 KB
TIM: about 192000KB
HOW COULD IT BE???
If is it confirmed, would it be legal to sell the same device with different characteristics without informing consumers?
Click to expand...
Click to collapse
if u look at the htc site u will see the original htc magic is listet with 288 mb ram
and the htc brandet witz 192mb ram
so why should this be not legale
kingchris said:
if u look at the htc site u will see the original htc magic is listet with 288 mb ram
and the htc brandet witz 192mb ram
so why should this be not legale
Click to expand...
Click to collapse
Well because to the most of people (consumers) is not asked to be PPC expert and informations should be done clearly, without doubts. So when I go to buy my Magic to Vodafone shop rather than to HTC or TIM shop I should know exactly what I am buying and what are the technical differences...and I also dare to exepct a different price. People generally know that HTC Magic is ONE and it is sold with two different brand (TIM - Vodafone), or no brand, and not that they are different devices technically speaking. Don't you think that if I should know it in advance I would buy the one with more ram at the same price???
EDIT:
and YES, I have checked it and it reports a different RAM amount between HTC and Vodafone...BUT once again, don't you think that this specific has been a little hidden in commercial comunication???
I've been wondering how to find the ram of an Android phone. I just opened /proc/meminfo and found this on my Google Ion:
MemTotal: 98328 kB
MemFree: 3260 kB
Buffers: 8 kB
Cached: 21776 kB
SwapCached: 0 kB
Active: 38508 kB
Inactive: 43660 kB
Active(anon): 30124 kB
Inactive(anon): 31568 kB
Active(file): 8384 kB
Inactive(file): 12092 kB
Unevictable: 1008 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 61416 kB
Mapped: 15660 kB
Slab: 3804 kB
SReclaimable: 760 kB
SUnreclaim: 3044 kB
PageTables: 4092 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 49164 kB
Committed_AS: 1114796 kB
VmallocTotal: 155648 kB
VmallocUsed: 65680 kB
VmallocChunk: 44028 kB
Click to expand...
Click to collapse
So it looks like my Ion has 192MB RAM (96MB for the OS, and the rest is shared with hardware). That's lame, especially for a second-generation, developer-targeted phone.
This is my Vodafone ITA with ION ROM.
MemTotal: 98356 kB
MemFree: 3288 kB
Buffers: 36 kB
Cached: 20996 kB
SwapCached: 0 kB
Active: 37936 kB
Inactive: 43640 kB
Active(anon): 26956 kB
Inactive(anon): 34864 kB
Active(file): 10980 kB
Inactive(file): 8776 kB
Unevictable: 964 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 61532 kB
Mapped: 16248 kB
Slab: 4180 kB
SReclaimable: 876 kB
SUnreclaim: 3304 kB
PageTables: 4044 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 49176 kB
Committed_AS: 1137064 kB
VmallocTotal: 155648 kB
VmallocUsed: 66660 kB
VmallocChunk: 21500 kB
Click to expand...
Click to collapse
Fatal1ty points out that:
- If the the first value is around 100MB it means it has 192 MB (baseband included)
- If the the first value is around 190 MB it means it has 288 MB (baseband included)
MemTotal: 98356 kB
MemFree: 4164 kB
Buffers: 36 kB
Cached: 23480 kB
SwapCached: 0 kB
Active: 38528 kB
Inactive: 43712 kB
Active(anon): 27148 kB
Inactive(anon): 32828 kB
Active(file): 11380 kB
Inactive(file): 10884 kB
Unevictable: 964 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 59712 kB
Mapped: 13048 kB
Slab: 3684 kB
SReclaimable: 844 kB
SUnreclaim: 2840 kB
PageTables: 4020 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 49176 kB
Committed_AS: 1059424 kB
VmallocTotal: 155648 kB
VmallocUsed: 65260 kB
VmallocChunk: 33788 kB
Italian Magic Vodafone with Noverca Rom
cat /proc/meminfo gives me the following results:
MemTotal: 98328 kB
MemFree: 3908 kB
Buffers: 112 kB
Cached: 19228 kB
SwapCached: 0 kB
Active: 36896 kB
Inactive: 44348 kB
Active(anon): 29336 kB
Inactive(anon): 33984 kB
Active(file): 7560 kB
Inactive(file): 10364 kB
Unevictable: 1008 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 62936 kB
Mapped: 11304 kB
Slab: 3900 kB
SReclaimable: 808 kB
SUnreclaim: 3092 kB
PageTables: 4028 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 49164 kB
Committed_AS: 1034044 kB
VmallocTotal: 155648 kB
VmallocUsed: 64652 kB
VmallocChunk: 21500 kB
Click to expand...
Click to collapse
Australian Magic Vodafone with SuperHeroV2 port by Fatal1ty2787 & NK02
I feel so duped, especially considering I am now, somewhat 'stuck' with this phone for the next two years. The reduced memory size on the Vodafone HTC Magic must be what is causing such huge slow downs whilst running the SuperheroV2 ROM...
my-demise said:
cat /proc/meminfo gives me the following results:
Australian Magic Vodafone with SuperHeroV2 port by Fatal1ty2787 & NK02
I feel so duped, especially considering I am now, somewhat 'stuck' with this phone for the next two years. The reduced memory size on the Vodafone HTC Magic must be what is causing such huge slow downs whilst running the SuperheroV2 ROM...
Click to expand...
Click to collapse
Same here.
But i dont think it should cause slowdowns?
If we're sure it does, i might go back to vodafone and claim false advertising. :-/
Ooops. I think, we're buggered.
HTC webpage has 2 magics one for vodafone one not.
clearly states in the specs of the VF has 192MB and on the regular 288MB
I bought my device from Vodafone Germany with Sapphire Rogers Rom:
MemTotal: 98356 kB
MemFree: 1904 kB
Buffers: 1940 kB
Cached: 18832 kB
SwapCached: 0 kB
Active: 39144 kB
Inactive: 43948 kB
Active(anon): 31844 kB
Inactive(anon): 31940 kB
Active(file): 7300 kB
Inactive(file): 12008 kB
Unevictable: 964 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 63308 kB
Mapped: 13612 kB
Slab: 4340 kB
SReclaimable: 1052 kB
SUnreclaim: 3288 kB
PageTables: 4492 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 49176 kB
Committed_AS: 1235236 kB
VmallocTotal: 155648 kB
VmallocUsed: 67316 kB
VmallocChunk: 19452 kB
Qualcomm® MSM7200A™ in HTC magic
Qualcomm® MSM7201a™ in the HTC magic from vodaphone
is there some difference?
looks like its manufacturing process. MSM7201A is 65nm chipset while the MSM7200A is manufactured on the 90nm process.
can anyone confirm?
So htc magic from vodaphone should drain less battery right? =)
You're correct in that it (Vodafone HTC Magic w/ Qualcomm® MSM7201a) will draw less power. In fact I was just about to post those finding now.
I guess in the future it'll be best to read the fine print haha!!
OT:
I suppose the lack of RAM isn't a HUGE deal as thankfully we can move all apps and dalvik-cache to the SDcard to free up what little RAM we already have. In fact I have seen great performance gains by moving all apps, cache and Rosie to my SD card.
192 and 288mb of RAM has nothing to do with the 512mb ROM.
moving apps and caches to your SD card isn't going to free RAM... it will free ROM space, which the Magic has plenty of (unlike the G1).
RAM is for apps that are currently running, and if you open too many it just saves their state and shuts them down until you switch back.
ROM is where everything is stored or "saved". So when you install an app its on your ROM, and when you launch the app it is STILL on your ROM, but is loaded into your RAM while running. I hope that helps the less savvy peeps.
That said, it is unfortunate that we have the 192mb models, as it will have to shut down apps and relaunch them more often... Down the road it might be limiting if we are porting ROMs from the Hero and the fancy interface needs more RAM than we have and things get sluggish. I will likely pickup a Hero as soon as one is available with US 3G bands.
Oh of course! Thanks for clearing that up. Everyone can disregard my previous post - well, except the part about the better power consumption of MSM7201a > MSM7200A
I don't know how to copy/ paste from the terminal emulator, but my HTC Magic with Rogers in Canada has:
Memtotal: 197144
Memfree: 5416
Active: 157248
I guess I should be happy... but at least you guys can root your phones!
Agggh. I created an account just to vent about this after reading this thread.
I cant believe I got so shafted by vodafone. I thought I was getting a phone with roughly the same performance specs as the hero, but instead I've got a dream without a keyboard!
This sucks.
Do you think its possible to upgrade the ram in the phone? Seriously.
diggyz said:
looks like its manufacturing process. MSM7201A is 65nm chipset while the MSM7200A is manufactured on the 90nm process.
can anyone confirm?
So htc magic from vodaphone should drain less battery right? =)
Click to expand...
Click to collapse
The MSM7200a is the 65nm version of the MSM7200 (90nm)
I couldn't find link from manufacturer to proof this, may be someone could.
So there is no difference in power consumption!
But i'm hear, that MSM7201A lacks ability to records vga with 30 fps due qualcomm patent problems.
Maybe it's part of the whole "with Google" initiative and not just Vodaphone. T-Mobile's going to have a "with Google" version, and it's only got 192 megs of ram. :-\ Well, guess this is a non-buyer for me.
http://www.engadget.com/photos/t-mobile-mytouch-3g-user-guide/2102338/
Here are the difference between the HTC and Vodaphone(T-Mobile?):
HTC Magic
Qualcomm® MSM7200A™, 528 MHz
ROM: 512 MB
RAM: 288 MB
Vodaphone
Qualcomm® MSM7201a™, 528 MHz
ROM: 512 MB
RAM: 192 MB
(According to the leaked manual, the MyTouch still has the Qualcomm® MSM7200A™, which tells me that there's actually 3 versions of the phone? If that's correct, then the specs for the T-Mobile version are as follows:
Qualcomm® MSM7200a™, 528 MHz
ROM: 512 MB
RAM: 192 MB
For reference, here's the HTC Dream (G1) and Hero Specs:
HTC Dream or T-Mobile G1
Qualcomm® MSM7201A™, 528 MHz
ROM: 256 MB
RAM: 192 MB
HTC Hero
Qualcomm® MSM7200A™, 528 MHz
ROM: 512 MB
RAM: 288 MB
Ps. Shouldn't this be in the regular section and out of the Dev area?
hmm, so I guess this is why the phone gets sluggish while using the media player, and actually closing down the download of the podcast app if switching to other apps.
I'm sure there is some way to make sdcard work as virtual ram? class 6?
bufodill said:
hmm, so I guess this is why the phone gets sluggish while using the media player, and actually closing down the download of the podcast app if switching to other apps.
I'm sure there is some way to make sdcard work as virtual ram? class 6?
Click to expand...
Click to collapse
If it's rooted, you could use swapper. It's an app that allows for a swapfile.
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):
Code:
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:
Code:
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
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!
Impressive!
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?
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
Amon_RA said:
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?
Click to expand...
Click to collapse
Do you mean that this may help track down why when 32a owners flash the 32b radio we lose all of our RAM?
Good luck man! I wish I can help with this technical stuff
biktor_gj said:
Trial and error
Click to expand...
Click to collapse
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?
@wire103: The way I see it, and the way it behaves so far, If I take a single byte reserved for the baseband, the kernel doesn't finish booting. It's easy to understand why, the kernel writes to a reserved address, then the baseband or a) gets corrupt and reboots or b) writes to the reserved address corrupting the data the kernel has written, so the kernel gets corrupt and reboots. In the end, if the phone ends up booting it means it all worked quite well. At the end of the reserved memory space, on other msm's at least, resides the audio tables (audioparam*.csv) the baseband uses to change between profiles (headset, earcouple and speaker). If I overwrite that, boom! the phone reboots, and start over again, or, in the best case scenario, it will break audio and reboot just the baseband losing phone connectivity, wich is obvious to see and to debug
On the kernel side, I can't mark anything as read only, I'm telling it that there IS more RAM so it can handle it, and that it's work in the end. And as I cannot get access to /dev/mem (since it's not there) I haven't found an easy fix to dump the entire memory.
@bcrook: I think it's not the radio what makes you loose ram, but the kernel itself. But without the HTC patches I cannot be sure until I see it. Although I can try to prepare some custom kernel with a little declared Ram to see if it helps booting a 32b kernel with a 32A radio.
In any case, 32A's original radio is version 3.22.20.17 and 32B radio is 2.22.19.26I so there might be some other things we don't know about.
And, so you all know what I know so far, 32A's kernel reports not 288 Mb of RAM as HTC Specification's page shows, but 198 Mb:
<6>[ 0.020000] Memory: 198MB = 198MB total
<5>[ 0.020000] Memory: 196608KB available (2824K code, 941K data, 104K init)
(taken from a dmesg some collaborative user posted on another thread)
So it seems in both cases, there's only one mapped bank, and it's eating about 80 mb of ram in both cases. Maybe these msm basebands need more ram to operate than previous models (I'm talking here about msm7201 vs msm7200). That's something I still don't know and I still have to test, but what I do know is that radios designed for both msm7200 and 7201 take more or less the same amount of space on flash (about 20mb), and on 7200 the needed ram for the baseband is 30mb, wich is way less than 80 mb wich is what this thing is eating.
EDIT: hmmm... I think I found the hole... shared memory (for gpu, camera...)
After looking at the code for the Diamond, Raphael and Blackstone, and after checking again the header files for the sapphire, I've seen that, apart from the baseband memory, wich will probably be 30 Mb more or less, other things are eating the ram. The most usable memory without corruption I can get is 109 Mb (11 mb more than stock kernels) without noticeable changes or problems (not that I've done a lot of debugging, but using the phone functions and opengl didn't give any problems of any kind)
So, we can take a little more RAM but not nearly as much as I thought.
For the code, in case anyone is interested, here you have:
Code:
if (smi_sz == 32) {
mi->bank[0].size = (84*1024*1024);
} else if (smi_sz == 64) {
mi->bank[0].size = (108*1024*1024);
} else {
printk(KERN_ERR "can not get smi size\n");
Or, if you want to tune it to the most you can get:
Code:
if (smi_sz == 32) {
mi->bank[0].size = (84*1024*1024);
} else if (smi_sz == 64) {
mi->bank[0].size = 0x06d00000;
} else {
printk(KERN_ERR "can not get smi size\n");
Almost anything above 0x06d00000 will make the phone reboot endlessly, and this will give you 109Mb of RAM. You can tune it further by altering the reserved memory addresses for the SMI, but I don't think that's a good idea (if they have those values it's for a reason, and you might end up seeing green lines on the screen, lockups, or other kind of errors by reducing the space for the framebuffer, adsp etc)
biktor_gj said:
@bcrook: I think it's not the radio what makes you loose ram, but the kernel itself. But without the HTC patches I cannot be sure until I see it. Although I can try to prepare some custom kernel with a little declared Ram to see if it helps booting a 32b kernel with a 32A radio.
In any case, 32A's original radio is version 3.22.20.17 and 32B radio is 2.22.19.26I so there might be some other things we don't know about.
Click to expand...
Click to collapse
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.
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
EDIT: nm, it is in the kernel source.
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...
biktor_gj said:
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...
Click to expand...
Click to collapse
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
Aweome if it works...
1 Lab Rat signing up for 32A!
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.
biktor_gj said:
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.
Click to expand...
Click to collapse
Doing it now, standby
biktor_gj said:
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.
Click to expand...
Click to collapse
so you want some one with a 32A to flash a 32B rom and then get the dmesg? or the origanal 32A?
Killadude said:
so you want some one with a 32A to flash a 32B rom and then get the dmesg? or the origanal 32A?
Click to expand...
Click to collapse
I need the 32B kernel dmesg when running on a 32A board
Sorry for my english...
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
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