MX1: obtaining the physical RAM, ROM, NAND size

[gavinca]

What exactly are stick PC owners using to determine the actual physical RAM/ROM/NAND size? I'm wondering how to explain to someone else how exactly to determine this for himself.

Oftentimes, the total RAM reported in System is about a quarter less than actual physical size. I suppose this is due to resources being allocated to the kernel or GPU in pre-boot.

As for the ROM and NAND size showing odd numbers on mine, I'm not sure. So does anyone have a way to determine the "vendor's website" specifications on their stick PC using an app, preferable without requiring root?

[Finless]

This is setup in the parameter file of the ROM.
In general count on the system taking about 1 meg of NAND (really about 800K).
/data is then setup. This is user APP space. When you boot up the device and look at storage the first part is the user data space. Manufacturers usually only give 512 to 1 meg of NAND for this but it could be anything. This is the area I increase ion my ROMs because 1 meg is usually not enough for large games.
The rest of NAND is used for Internal SDcard.

So really there is no way to tell unless you boot it up and look how the parameters are setup.

Bob

[gavinca]

This is setup in the parameter file of the ROM.
In general count on the system taking about 1 meg of NAND (really about 800K).
/data is then setup. This is user APP space. When you boot up the device and look at storage the first part is the user data space. Manufacturers usually only give 512 to 1 meg of NAND for this but it could be anything. This is the area I increase ion my ROMs because 1 meg is usually not enough for large games.
The rest of NAND is used for Internal SDcard.

So really there is no way to tell unless you boot it up and look how the parameters are setup.

Bob

Thank you Bob. By the way, are you referring to this file? /system/build.prop?

[Finless]

Thank you Bob. By the way, are you referring to this file? /system/build.prop?

No, if you download one of my ROMs and look in the FinlessROM folder you will see a file called parameter. This can be opened as a text file. This sets up the partitions in NAND. You cannot see this as a file in Android because it is only used by the flash tool.

In Android to see the partition sizes, you need to install a terminal emulator and do this command
cat /proc/mtd

Bob

[cyberhost]

No, if you download one of my ROMs and look in the FinlessROM folder you will see a file called parameter. This can be opened as a text file. This sets up the partitions in NAND. You cannot see this as a file in Android because it is only used by the flash tool.

In Android to see the partition sizes, you need to install a terminal emulator and do this command
cat /proc/mtd

Bob

OMG are you saying that the internal memory that is displayed in "settings / storage" is setup via the parameter file?

Does this apply to my question here?

http://www.freaktab.com/showthread.php?3669-Need-help-with-memory-bug&p=50044#post50044

Also in the parameter file I see it starts with MTD then the file rk29xxnand.

Now I see there is a file by that name in the bootloader. What is the purpose? Does that file not also dictacte the physical memory?

[Finless]

OMG are you saying that the internal memory that is displayed in "settings / storage" is setup via the parameter file?

Does this apply to my question here?

http://www.freaktab.com/showthread.php?3669-Need-help-with-memory-bug&p=50044#post50044

Also in the parameter file I see it starts with MTD then the file rk29xxnand.

Now I see there is a file by that name in the bootloader. What is the purpose? Does that file not also dictacte the physical memory?

Yes and yes... If you have the wrong rkxxnand.ko file it can display incorrect total NAND.

Bob