Is there a way to have all 768gb of RAM available?

[frellingfrakker]

OK, I know that on stock Thunderbolts you can only ever see 582gb of RAM available with the explanation being that in the stock ROM HTC allocates the remaining RAM for SENSE and/or the system so it does not show up in the total. This being the case I thought that if I rooted my Bolt and installed a different ROM and kernel (specifically AOSP) that the device would now actually show that there is 768mb of RAM but this is not the case. Does anyone know if it is even possible to "expose" all the RAM in a modified kernel or ROM?

BTW, I'm running Liquid Gingerbread 3.2.

 

[frellingfrakker]

Also, what about all 8gb of internal storage?

 

[fatboy97]

OK, I know that on stock Thunderbolts you can only ever see 582gb of RAM available with the explanation being that in the stock ROM HTC allocates the remaining RAM for SENSE and/or the system so it does not show up in the total. This being the case I thought that if I rooted my Bolt and installed a different ROM and kernel (specifically AOSP) that the device would now actually show that there is 768gb of RAM but this is not the case. Does anyone know if it is even possible to "expose" all the RAM in a modified kernel or ROM?

BTW, I'm running Liquid Gingerbread 3.2.

768mb... NOT 768gb!!!

Short answer... no, you will not be able to see the entire 768mb or the 8gb of internal storage. Maybe someone else has the bigger picture explanation on exactly why not. I'm sure some of this is available for radio files, recovery and other apps, plus the ROM, cache, dalvik cache and data files for all the apps.

 

[frellingfrakker]

768mb... NOT 768gb!!!

Short answer... no, you will not be able to see the entire 768mb or the 8gb of internal storage. Maybe someone else has the bigger picture explanation on exactly why not. I'm sure some of this is available for radio files, recovery and other apps, plus the ROM, cache, dalvik cache and data files for all the apps.

Oops, sorry about the gb typo, I DO know the difference

Yeah, I know this has been an ongoing discussion since the TB came out but I just decided to root last week and thought a custom kernal may have resolved it.

 

[defcon999]

it goes back years and years. The OS needs some overhead to boot-up and cache out. The manufactures should just call for example USB Thumb-drive that is 8GB in reality "7.23GB"....but that doesn't look SEXY on the packaging.

I think there should be a NIGEL TUFNEL moment here "Why don't you just make 10 the loudest?"......"this one goes to 11".

 

[FrankXS]

768mb... NOT 768gb!!!

Short answer... no, you will not be able to see the entire 768mb or the 8gb of internal storage. Maybe someone else has the bigger picture explanation on exactly why not. I'm sure some of this is available for radio files, recovery and other apps, plus the ROM, cache, dalvik cache and data files for all the apps.

Yeah, plus the screen video driver.

-Frank

 

[jstewart0131]

it goes back years and years. The OS needs some overhead to boot-up and cache out. The manufactures should just call for example USB Thumb-drive that is 8GB in reality "7.23GB"....but that doesn't look SEXY on the packaging.

I think there should be a NIGEL TUFNEL moment here "Why don't you just make 10 the loudest?"......"this one goes to 11".

The analogy to the thumb drive isn't quite right. For marketing purposes company's consider 1 gigabyte as 1,000 megabytes. This isn't exactly true since a true gigabyte is 1024 megabytes. You 8gb drive is marketed as 8,000 megabytes which translates to an actual 7.8125 gigabytes. Further confusing this is that you have to take up a portion of the available memory to create the master file table. This is what becomes the index of where files are stored on the drive. This happens when you format the drive. The amount taken up by formatting varies by the formating standard uses (fat32, ntfs, etc).


Back to the OP's question. You'll never see 768mb available because you have to load the OS, and any applications into RAM in order for the device to function. The less complex the OS, the less ram it will use up. This is why AOSP roms use less ram than full sense roms.

 

[defcon999]

The analogy to the thumb drive isn't quite right. For marketing purposes company's consider 1 gigabyte as 1,000 megabytes. This isn't exactly true since a true gigabyte is 1024 megabytes. You 8gb drive is marketed as 8,000 megabytes which translates to an actual 7.8125 gigabytes. Further confusing this is that you have to take up a portion of the available memory to create the master file table. This is what becomes the index of where files are stored on the drive. This happens when you format the drive. The amount taken up by formatting varies by the formating standard uses (fat32, ntfs, etc).


Back to the OP's question. You'll never see 768mb available because you have to load the OS, and any applications into RAM in order for the device to function. The less complex the OS, the less ram it will use up. This is why AOSP roms use less ram than full sense roms.

Yes, you are right.....most people don't care or know about that 1024 bytes is actually a Megabyte and 1024 Megabytes are a Gigabyte and 1024 Gigabytes are a Terabyte and 1024 terabytes are a Petabyte...I usually lose my audience (parents) after Megabyte.

I wonder how many people write complaint letters saying their thumbdrive is bad.....LOLOL....better than calling about the cupholder not working anymore!