yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Q&A, Help & Troubleshooting] sionyboy:
Here;

http://xdaforums.com/showthread.php?t=762116&page=2

Read through that thread for some real detective work as to where our missing memory is, as opposed to conjecture, hearsay and name calling ;-). 128mb is being used as a ram disk. Obviously there is always going to be memory reserved by the system for basic telephony/communications, so we'll never see the full 512mb available, but if some of the xda gurus can get onto ffreeing up some of this (pointless) ran disk we will start to see an improvement (If it's possible of course!)
[Galaxy S I9000 Q&A, Help & Troubleshooting] vitalij:
Well in this thread they are saying that memory is used for /dbdata ram disk. However, /dbdata is definitely not a ram disk - it keeps data after reboot. I think that galaxy s really have less than 512 mb ram.
[Galaxy S I9000 Q&A, Help & Troubleshooting] irkkso:
The tmpfs in Froyo is less than in Excalir it means that it option tunable?

The tmpfs in Froyo is less than in Excalir it means that it option tunable?
[Galaxy S I9000 Q&A, Help & Troubleshooting] vinclar:
Is there any video of galaxy S dismmanteled? Because there maybe we can see the chips and see if physically it hast that ammount of memory, and see if its no 384ram+128vram=512ram this sum of marketing magicians, or its 512Mb of ram and maybe 128mb vram.

Here is a disassembly of our galaxy S.

http://www.careace.net/2010/06/09/disassembly-of-the-samsung-galaxy-s/
[Galaxy S I9000 Q&A, Help & Troubleshooting] Bumble-Bee:
There is no VRAM !!!! lol

@neldar

anyone tried changing those sizes or know what they are being used for ?
[Galaxy S I9000 Q&A, Help & Troubleshooting] alban_:
(sorry, still cannot post links)

According to this page: w w w. ubmtechinsights. com /reports-and-subscriptions/investigative-analysis/samsung-galaxy-s/

and this page: w w w. eetimes. com /electronics-news/4206197/Samsung-s-Galaxy-S-smartphone--What-s-under-the-AMOLED-semiconductor?pageNumber=1

The memory modules contained in the CPU package are:

KFG8GH6Q4M (8 Gb of OneNand): 1GB

K4X2G323PB (2 Gb of DDR SDRAM): 256MB

K4X1G323B (1 Gb of DDR SDRAM): 128MB

Another 1-Gb die: another 128MB

So it looks like 1GB of NAND is used for storage (see this post: xdaforums.com/showpost.php?p=7635022&postcount=2)

and there are 512 MB of RAM, split in 3 parts. Maybe some of it is reserved for the GPU or other hardware, the rest is available to the kernel.
[Galaxy S I9000 Q&A, Help & Troubleshooting] rocasper:
I think Samsung just f$@#ed us for a little more profit... That is the harsh reality...

This device is just not usable for me because of this handicap (just try to keep yahoo apps opened on it to see if you can do anything else)... So... Samsung = all show but no substance. This marketing strategy can function once... but the second time you can bett your ass I will go with HTC or Motorola!
[Galaxy S I9000 Q&A, Help & Troubleshooting] OrionBG:
Sorry for repeating something that have already been written here but the Galaxy tab uses the exact same hardware as the SGS and still there is almost 100MB difference in ram capacity on both so something can be done! It is just a matter of time before someone get the Galaxy Tab firmware and dismantle it!
[Galaxy S I9000 Q&A, Help & Troubleshooting] jaju123:
Just wait for the open source 2.2 release and then we will start seeing a lot more ROMs and fixes for all the problems this phone has. As of now it is still very fast with Voodoo lag fix and it's the best ive seen on JM8. Froyo is a bit 'meh' at the moment but I have every confidence in the community for the future :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] sionyboy:
I'm hoping that once 2.2 gets an official release the modders will spring into action and start really hammering out the issues in this phone. Changes to file system, memory management etc... having the tab kernel will be a great help as well.

Course, maybe Samsung will do the job for them but..... yeah. Porky hasn't developed wings yet.
[Galaxy S I9000 Q&A, Help & Troubleshooting] flypubec:
Today I played with HTC desire to get out-of-memory problem with my flash app that uses 130Mb of RAM and won't open on fully mem cleaned SGS.

The results:

Could not do it ! :eek:

I've opened about 20 other apps, but there was always enough mem left when i ran the flash app in the browser. Looked like apps were freeing up some memory when running in the backgound.
[Galaxy S I9000 Q&A, Help & Troubleshooting] rocasper:
I think that they realized the error of their ways with the tab and put more ram in it. Has someone actually examined the mobo in the tab? Anyway it is too late for us...
[Galaxy S I9000 Q&A, Help & Troubleshooting] thunderteaser:
Why? Are we gonna die? :eek:
[Galaxy S I9000 Q&A, Help & Troubleshooting] rdy2go:
Hope dies last.
[Galaxy S I9000 Q&A, Help & Troubleshooting] boliveira2:
It's already over.

It's already over...

Could you turn on the train and play Venus song? Thank you.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Intratech:
The Tab doesn't have the touchwiz crap so maybe that accounts for some of the extra RAM available on it.
[Galaxy S I9000 Q&A, Help & Troubleshooting] neldar:
I managed to gain some ram by reducing the amount of memory that is allocated in bootmem for variuos drivers/devices.

If want to test it yourself you should build your own kernel and chance this values in the config:

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=6144
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=6144
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=16384
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=16384

edit:

ok, that is not useful, mfc values are necessary for video recording (codec).
[Galaxy S I9000 Q&A, Help & Troubleshooting] Oletros:
Tab has Touchwiz 3.0 like the Galaxy S
[Galaxy S I9000 Q&A, Help & Troubleshooting] blackdeath09:
Why if there is K4X2G323PB (2 Gb of DDR SDRAM) there is enabled only 256 mb. Am I missing something?
[Galaxy S I9000 Q&A, Help & Troubleshooting] Oletros:
2 Gbit = 256 Mbyte
[Galaxy S I9000 Q&A, Help & Troubleshooting] PlanetJumble:
2 Gibibit (often wrongly referred to as Gigabit) of SDRAM are exactly 256 Mebibyte (often wrongly referred to as Megabyte). :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] azreil24:
Could it be that the Personal Data memory is part of the RAM? Just asking :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] bilboa1:
- create new units standard with same shortcuts but bigger values

- use the shortcuts

- profit!

hate the industry :P
[Galaxy S I9000 Q&A, Help & Troubleshooting] PlanetJumble:
Actually, it was just a collision of multiplication prefixes. Since the early computer days, kilo was used for a multiple of 1024 (and so on with mega and giga). That was because most everything computer related is based on powers of 2.

But these prefixes are much much older than computers and are standardized as a factor of 1000 (million, billion and so on). So the industry didn't invent those new prefixes to rip you off, but because the other ones were simply misused.

Note I am not saying that the marketing departments didn't abused this confusion, they still do. :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] blackdeath09:
I see. Is stupid somehow because everyone knows gb as gigabyte and mb as megabyte. So there is a conversion of values from the standard ram memory unit to classic memory unit. This thing really sucks. It can trick you really easy.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ivanchin99:
:confused: Installed yahoo mail app, run it in the background and have 88mb free
[Galaxy S I9000 Q&A, Help & Troubleshooting] azreil24:
As a comparison, don`t know if it is a good one as both devices are not in the same performance chart, but the HTC wildfire has 218 MB free out of 256. My HD2 had 384 free, ~430MB visible out of 512MB. Gues Samy left out some of the memory :))
[Galaxy S I9000 Q&A, Help & Troubleshooting] karayemis:
Samsungs own task manager (1.5) shows that hij have 304mb of ram. so where is the 208 mb ram ? some people are talking about 384 ram i cant see that all that it shows is 304mb of witch 180 is in use.
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
And I'm guessing you guys are all making assumptions over pre-beta firmwares.
[Galaxy S I9000 Q&A, Help & Troubleshooting] andars05:
The current stock firmwares only have about 324~mb available. The Froyo ones (although beta), show even less. I don't think you can really blame people for not giving Samsung the benefit of the doubt. I don't think they will fix it for the final Froyo release.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ardf69:
From /proc/iomem of JPK

$ cat /proc/iomem

30000000-34ffffff : System RAM

302d5000-30bd6fff : Kernel text

30c30000-30e0d8ab : Kernel data

35000000-35ffffff : onedram

35000000-35ffffff : onedram

40000000-4fffffff : System RAM

50000000-57ffffff : System RAM

The mapping is really strange; we have:

30000000-34ffffff 80 MB RAM for the kernel code

35000000-35ffffff 16 MB of onedram (it's a kind of shared memory)

40000000-4fffffff 256 MB RAM

50000000-57ffffff 128 MB RAM

The strange thing is 80MB (nor 64 MB nor 128 MB). For 512 MB of ram 32 MB lacks.

Ciao Angelo
[Galaxy S I9000 Q&A, Help & Troubleshooting] frewys:
Lets hope for the best. There might be a lot of debugging code hiding in Beta Froyo. But coming from Nexus one with... Its a sad story...

Really a shame the company's are not forced to give naked Froyo as an option.
[Galaxy S I9000 Q&A, Help & Troubleshooting] biktor_gj:
80 mb for the kernel is fine to me. There you have the reserved memory gor the gpu, adsp, shared mem for the radio etc.

And you guys are forgetting that the radio runs a separate OS, which consumes about 100Mb of RAM on this phone.

Some more examples:

HTC Nike: Total RAM: 128 Mb. Available to the user 90.

HTC Magic: 192 Mb of RAM. Available to the user, about 110.

Xperia X10: Total RAM: 384Mb. Available to the user: 270Mb aprox.

Galaxy S: Total RAM: 512. Available to the user: 311Mb

It's not only froyo what consumes memory, there are a lot of things inside of the phone, and everything needs some ram to work. And the bigger the screen, the bigger gpu mem, normally.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Maddmatt:
Using "Naked Froyo" doesn't change the fact that they have to write their own drivers and adapt Android to their hardware.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Einride:
Really? 100 MB for just the radio OS? In what world is this acceptable? Is the damn radio running Windows ME? 100 MB for just that one component is ridiculous! If they used 100 MB for the kernel and all hardware components in total, I could understand, but ~200 MB? Insanity...

And there isn't really 311 MB available for the user is there? I've NEVER had more than ~220 MB available and that's with a bare minimum of applications and services running.

Everyone's throwing out "facts" about the PowerVR GPU sharing some of the RAM, but nobody has anything to back it up. A couple of google searches for the hummingbird architecture and/or SGX540 doesn't state anything about RAM/VRAM at all. In fact, there's not much information other than marketing talk about it being "faster than anything else" :rolleyes:

Either Samsung has borked it up on the hardware side and can't "fix" this issue or it's a software issue which they're just not focusing on for the time being (or ever).
[Galaxy S I9000 Q&A, Help & Troubleshooting] flypubec:
If Samsung does not give me fair ammount of RAM with the first official Froyo release, I am returning the phone and starting some serious badass publicity on Samsung. :cool:
[Galaxy S I9000 Q&A, Help & Troubleshooting] mundano:
Wildfire has no GPU...
[Galaxy S I9000 Q&A, Help & Troubleshooting] ardf69:
I know 80MB are ok for the kernel. The problem is the size of the block that is 80 MB and subsequent contiguous block is 16 MB.

Ciao Angelo
[Galaxy S I9000 Q&A, Help & Troubleshooting] mbr01:
I don't believe people claiming that the radio needs 100MB of RAM. It's ridiculous. There are phones around with far less memory capable of exactly the same connectivity. Frankly if I'd guess it probably is 10MB maximum.

So the Memory must be somewhere else.
[Galaxy S I9000 Q&A, Help & Troubleshooting] andrewluecke:
Thats just recycled information anyway.. I haven't seen anyone find conclusive evidence where it's being used . But hopefully someone pulls the software apart to get to the truth.
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheBeano:
This is where it goes, from dmesg run straight after startup under JPK:

[ 0.000000] CPU S5PV210/S5PC110 (id 0x43110222)
...
[ 0.000000] s5pv210: 37748736 bytes system memory reserved for mfc at 0x30ec2000
[ 0.000000] s5pv210: 37748736 bytes system memory reserved for mfc at 0x40204000
[ 0.000000] s5pv210: 14680064 bytes system memory reserved for fimc0 at 0x42604000
[ 0.000000] s5pv210: 1048576 bytes system memory reserved for fimc1 at 0x43404000
[ 0.000000] s5pv210: 12582912 bytes system memory reserved for fimc2 at 0x43504000
[ 0.000000] s5pv210: 16777216 bytes system memory reserved for pmem at 0x332c2000
[ 0.000000] s5pv210: 10485760 bytes system memory reserved for pmem_gpu1 at 0x342c2000
[ 0.000000] s5pv210: 1536000 bytes system memory reserved for pmem_adsp at 0x34cc2000
[ 0.000000] s5pv210: 5132288 bytes system memory reserved for jpeg at 0x44104000
[ 0.000000] s5pv210: 10485760 bytes system memory reserved for texstream at 0x445e9000
[ 0.000000] s5pv210: 3145728 bytes system memory reserved for fimd at 0x44fe9000
[ 0.000000] s5pv210: 262144 bytes system memory reserved for wifi at 0x34e39000
[ 0.000000] Built 3 zonelists in Zone order, mobility grouping on. Total pages: 117856
[ 0.000000] Kernel command line: console=ttySAC2,115200 loglevel=4
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 80MB 256MB 128MB = 464MB total
[ 0.000000] Memory: 308048KB available (9224K code, 1910K data, 2868K init, 0K highmem)

Total of "system memory reserved" is 143MB. A bit of digging in the kernel source should reveal exactly what each item is.
[Galaxy S I9000 Q&A, Help & Troubleshooting] ntomi:
I didn't have time to read the whole thread, but i think that all these RAM issues are not being discussed properly. Let us be clear on our statements and proofs. Please, you should do this: tell about amount of RAM installed, then RAM accessible from the software a.k.a phone it seft (not including GPU or other hardware) and last RAM left FREE after the boot accessible by applications. This would clear up thing for the vast majority of people.

So, someone that has some info for some high-end smarts please sort it like this (in four columns). It will help get the difference:

RAM installed | Hardware reserved | RAM recognized by phone | RAM free

------------------------------------------------------------------------

Samsung G S 512MB | 192MB | 3xx | 1xx

HTC Wildfire

Nexus One

etc.

Thank you :)
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheBeano:
The top 5 (99MB total) are all for video, MFC is "Multi Function Codec", FIMC is the cameras.
[Galaxy S I9000 Q&A, Help & Troubleshooting] xan:
So.... it looks that memory is reserved for hardware accelerated video encoding / decoding, hardware jpg decoder.. 128-80 =48 for baseband?

Wild guess and speculation.
[Galaxy S I9000 Q&A, Help & Troubleshooting] andars05:
I'm hoping some smart devs can figure out how to reduce the memory usage. It would be interesting to see whats taking up more memory in 2.2 vs 2.1 (304mb vs 324mb).
[Galaxy S I9000 Q&A, Help & Troubleshooting] vinclar:
For me the problem isn't that the phone is showing 20MB less in "beta froyo", the problem is only we have around 100MB usable, and I specs say 512MB ram, thats a joke? I feel cheated and unhappy with my phone.

Why samsung isn't able to make good software (lag/no JIT opt/mono radio/bloatware instead of sth like Sense/GPS signal lost), for now i'm fully deceived of my phone.

Official froyo is my last hope to have this things solved.
[Galaxy S I9000 Q&A, Help & Troubleshooting] deathst:
Well Google says

FOR 2.1

For 2.2

Found in http://static.googleusercontent.com...oid.com/en//compatibility/android-2.1-cdd.pdf and

http://static.googleusercontent.com...oid.com/en//compatibility/android-2.2-cdd.pdf
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheBeano:
The current config has more than 300MB available for kernel and userspace, and /data is 2GB, so it more than meets all those requirements.
[Galaxy S I9000 Q&A, Help & Troubleshooting] bilboa1:
"not under kernel control" => the tradional blackhole'd memory on such devices

and yeah it fits the minimum requirements

but like everyone, i'd like if they didn't blackhole like 180megs of ram so that I could use it, as many point out we do get out of memory errors easily and there's no good reason for this ram not to be available.. except a hardware issue worked around by software.. dum dum dum
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheBeano:
It isn't blackholed, it's reserved for various hardware and codec-related tasks as shown in http://xdaforums.com/showpost.php?p=8366849&postcount=136
[Galaxy S I9000 Q&A, Help & Troubleshooting] DataSpree:
I keep seeing people claim that these Galaxy S phones have 512MB of memory installed in them. From what I see in this output and in the kernel output of my SCH-i500 it appears there is only 464MB of RAM which is then further reduced to 300-321MB of RAM for userspace (OS + applications). I'm starting to get tempted to take apart my phone so I can see, and photograph, exactly what memory chips are on these phones.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lugi93:
Already done by few..just google :rolleyes:

http://www.phonewreck.com/2010/08/19/samsung-galaxy-s-teardown/
[Galaxy S I9000 Q&A, Help & Troubleshooting] lokhor:
I'm not entirely sure but that article at phoneWreck only mentions:

K4X1G323B 1GB DDR

K4X2G323PB 2GB DDR

if GB = Gigabit then that is 3072Mbit/8= 384 Megabytes of RAM
[Galaxy S I9000 Q&A, Help & Troubleshooting] TheBeano:
It's wrong, the whole block diagram seems to be wrong. This teardown says there are three DDR RAM chips in the stack, 2x1Gbit and 1x2Gbit, and this matches the three blocks of RAM reported by the kernel. One of the blocks is missing 48MB and presumably this is used by the radio, you would need the bootloader source to be sure I think.
[Galaxy S I9000 Q&A, Help & Troubleshooting] lokhor:
How much memory do devices like the HTC Desire have?
[Galaxy S I9000 Q&A, Help & Troubleshooting] rod90:
in Super Manager Task Manager it shows I have 40 'things' running using up all kinds of memory but the core system services alone add upto 311mb.

the default task manager shows 206/326mb in use. I bet if I were to add up all the services and apps running in the Super Manager it might add up
[Galaxy S I9000 Q&A, Help & Troubleshooting] masterotaku:
Fortunately PowerVR's base architecture has been around for way more than a decade, so there are some things you can conjecture. PowerVR cores do have to have a small non framebuffer cache to deal with tile deferment and z-occlusion/culling. Other PowerVR architecture devices (Intel GMA500/600 onboard video, iPhone3gs, 4) for example do this. It's a trivial amount of ram to get bent out of shape about on an intel integrated chipset, but perhaps one to be concerned with on a phone.

Still, iOS4 on an IP4 doesn't boot with much more mem than we do, but it is still more. I'd like to think however that there is no conspiracy theory here, that dogs and cats are not going to start living together, and that Samsung left this hole in the memory map of the OS for perfectly valid reasons to support necessary code running on their SoC, outside of the OS.
[Galaxy S I9000 Q&A, Help & Troubleshooting] di11igaf:
not really..my galaxy s boots now with froyo with about 140-150mb free ram..i also after booting purged the ram in task manager i killed everything that could be killled and the most that well ever actually see is around 160-170mb's. here is a screen shot of what my iphone 4 had

it was booting with 350mb's of user accessible ram. i could do what i wanted with that 350 mb of free ram.. my galaxy s boots with 140 mb's of user accessible free ram. so thats a difference of over 200 mb. i would say that is much more. out of 140, the launcher takes 20, i just did a test with my browser..4 large pages open, 140mb..opened task manager to see it. it was red in task manager which id never seen that so it closed the browser. so multitasking on this phone is pretty much non existent with 140 mbs available. thats really ****ing rediculous. i love this phone but im starting to hate samsung
[Windows Mobile] mikentucson:
i've started cooking my own roms & have gotten the rom pretty much setup the way i want it.. only thing i have left to do is cook in my activesync settings. i dont like going in and adding the server source, login username, password, sync settings, etc.. is there an app or way to cook in these settings? thanks in advance :)

edit: and i use DIY Kitchen BuildOS_Utility 2.4.1
[Windows Mobile] crazyC:
My advice would be to find a template - they are around - or use something like Sashimi to create an xml to do it. I would then install it off my storage card using XDA-UC.

Well thats how I do it.
[Windows Mobile] mikentucson:
thanks i'll check that out
[Windows Mobile] Farmer Ted:
You can back all that stuff up with sk tools.
[Sony Ericsson XPERIA X10 Mini] sirmarcelot:
hi

i have a x10 mini, and i have to tell you, i was happy with it, but over and over i get frustrated. first i had the issue with my sim card (cant turn on with sim card on, after i updated the firmware)... and now i've noticed another problem =\

the issue is the following: the accelerometer seems to be way off! when i run games like Speedx, i notice that even with the phone on a 100% leveled support, the controls are off to the right.. this is very annoying

does anyone know of a way to calibrate it ? system wide i mean. some apps allow you to calibrate but it is only relative to the application itself. is there any hack or secret menu??

there is a supposed calibrate for the compass in the service menu, but i do not think it has anything to with it. help please?
[Sony Ericsson XPERIA X10 Mini] sirmarcelot:
no one here had problems with the accelerometer? seriously?
[Sony Ericsson XPERIA X10 Mini] sirmarcelot:
shameless self bump

come on, no one has this issue?
[Sony Ericsson XPERIA X10 Mini] VooDoo`:
I don't know if we could calibrate the sensor, but you can check the calibration in service menu or install the app "gps status".

This app shows a little yellow circle, this should be nearly in the middle of the circular line). on my mini the y-axis is a little bit off the norm. the apps allows a calibration, but this should only work for the app itself (I think).
[Sony Ericsson XPERIA X10 Mini] sirmarcelot:
i've tried that calibration but i dont think it affects the accelerometer? i think its not the same thing as the compass
[Sony Ericsson XPERIA X10 Mini] VooDoo`:
I think it should be the possibility to calibrate the sensor, at my aino the accelerometer-x-axis was totaly out of range.

perhaps you can reach more at the sony-ericsson forums.
[Sony Ericsson XPERIA X10 Mini] darfito:
I have the same question... how hell is it possible to reset or calibrate de accelerometer sensor...

Everything is ok, but i noticed when i use the Google Sky Map app, the horizon isn't flat, it has about 30º of error...

Please, any help? :(
[Sony Ericsson XPERIA X10 Mini] sirmarcelot:
shameless self bump. last one i promess =p

no one knows of a calibration solution? maybe some messing around with root stuff?
[Sony Ericsson XPERIA X10 Mini] wolframio74:
same here, some devices got a global tilt calibration tool, some samsung devices got a command tool called "sensorcalibutil_yamaha"... but i cant find a general tool for the X10 or others devices.