yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] K4P1:
Just some detailed (and useless) information about memory mapping.

fw is 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

e1600000-e1600fff : s3c-keypad

e1600000-e1600fff : s3c-keypad

e1700000-e1700fff : s3c-adc

e1800000-e1800fff : s3c2410-i2c.0

e1800000-e1800fff : s3c2410-i2c

e1a00000-e1a00fff : s3c2410-i2c.2

e1a00000-e1a00fff : s3c2410-i2c

e1b00000-e1b00fff : s5p-cec

e2700000-e27000ff : s3c2410-wdt

e2700000-e27000ff : s3c2410-wdt

e2800000-e28000ff : s3c2410-rtc

e2800000-e28000ff : s3c2410-rtc

e2900000-e2900100 : s5pv210-uart.0

e2900000-e29000ff : s5pv210-uart

e2900400-e2900500 : s5pv210-uart.1

e2900400-e29004ff : s5pv210-uart

e2900800-e2900900 : s5pv210-uart.2

e2900800-e29008ff : s5pv210-uart

e2900c00-e2900d00 : s5pv210-uart.3

e2900c00-e2900cff : s5pv210-uart

eb000000-eb000fff : s3c-sdhci.0

eb000000-eb000fff : mmc0

eb100000-eb100fff : s3c-sdhci.1

eb100000-eb100fff : mmc1

eb200000-eb200fff : s3c-sdhci.2

eb200000-eb200fff : mmc2

ec000000-ec0fffff : s3c-usbgadget

eee30000-eee300ff : s3c64xx-iis.0

eee30000-eee300ff : s3c64xx-i2s

f1700000-f17fffff : s3c-mfc

f1700000-f17fffff : s3c-mfc

f8000000-f80fffff : s3cfb

f8000000-f80fffff : s3cfb

f8200000-f8207fff : ielcd

f9000000-f90fffff : s5p-tvout

f9000000-f90fffff : s5p-tvout

f9100000-f91fffff : s5p-tvout

f9100000-f91fffff : s5p-tvout

f9200000-f92fffff : s5p-tvout

f9200000-f92fffff : s5p-tvout

fa000000-fa0fffff : s5p-g2d

fa000000-fa0fffff : s5p-g2d

fa100000-fa1fffff : s5p-tvout

fa100000-fa1fffff : s5p-tvout

fa600000-fa6fffff : s3c-csis.0

fa900000-fa9003ff : s5p-tvout

fa900000-fa9003ff : s5p-tvout

fab00000-fab00fff : s3c2410-i2c.1

fab00000-fab00fff : s3c2410-i2c

fae00000-fae00fff : mdnie

fb200000-fb2fffff : s3c-fimc.0

fb200000-fb2fffff : s3c-fimc

fb300000-fb3fffff : s3c-fimc.1

fb300000-fb3fffff : s3c-fimc

fb400000-fb4fffff : s3c-fimc.2

fb400000-fb4fffff : s3c-fimc

fb600000-fb6fffff : s3c-jpg

fb600000-fb6fffff : s3c-jpg

fb700000-fb7fffff : s3c-ipc

fb700000-fb7fffff : s3c-ipc
[Galaxy S I9000 Android Development] lemmy_0:
that's great news.

you used google maps?

or another application?
[Galaxy S I9000 Android Development] Whitykoeln:
What Navigationprogram did you use? I tried Navigon 3.5 with JPK yesterday and it was a catastrophy.
[Galaxy S I9000 Android Development] pharaohdk:
you want hard evidence? well go on and dissasemble your phone. Find the ram modul then find a way to make it show how big it is.

Are you saying samsung lied when saying spec was 512 mb ram?
[Galaxy S I9000 Android Development] BMWpokerAce:
Sorry for the Q.

But why is it not poss. to upload this FW?

Is there no way to get it from the Phone?
[Galaxy S I9000 Android Development] pharaohdk:
the guy does not have root it, since it require him to flash a new kernal to apply root. And sadly he is not able to get the JP4 kernal back onto the phone. so no way for him to mack a backup.
[Galaxy S I9000 Android Development] JohnDogget:
I read all the BS about SGS and I decided to sell ASAP this ****.... ;( I am really disappointed.
[Galaxy S I9000 Android Development] pharaohdk:
point of post being what?
[Galaxy S I9000 Android Development] lgkahn:
ya right.. b.s. you saying that no further devel. is going to be done between now and end of oct.. i call b.s.
[Galaxy S I9000 Android Development] SKeijmel:
Well i got firmware xwjm2 and my phone runs fine and no lag either. i get a quick gps fix and it works acurate in car with google navigation en sygic mobile maps. i dont get all the fuzz about problems with this phone ill waith the the official update will be put thru kies and then ill update it, to feel the improved performance. but my phone is perfect at the moment just the way it is, and it runs psx games in emulator which is quite cool!
[Galaxy S I9000 Android Development] krazyphire:
Do you think you could post a mytracks of the google maps?
[Galaxy S I9000 Android Development] Ibanez33:
He would need to flash an old kernel still as the newer version of the recovery will only accept update.zip's that have been signed by samsung. Which the reason for needing to flash an old kernel to root..

Nice idea though....

:) How come there isn't 512mb of ram!!! (sorry couldn't help myself lol)
[Galaxy S I9000 Android Development] googlymoogly:
People wonder about the RAM because:

1) Other phones tend to have more RAM available, like for example the Nexus One.

2) Because there is something that (is, so far, little understood) makes the phone lag whenever you go below 50-60 MB free RAM, which other phones do not get, irrespective of if you use a lagfix or not. So, SGS has actually even less free usable RAM if you look at it that way, and every additional MB from the start would help.
[Galaxy S I9000 Android Development] freakonaleash:
i'm gonna crazy now :D
[Galaxy S I9000 Android Development] Einride:
Err, no, you misunderstood :)

That was directed at those who are coming up with these facts that 100 MB of system RAM is used by the radio, XX MB is used by the GPU, six MB is used by gremlins in the phone and so on. Yet the facts surrounding these statements are sparse at best.

Samsung states that the phone has 512 MB RAM, yet we're only seeing ~311 MB of those, and even less of that again is available for user applications. If Samsung had just stated that the phone has 384 MB RAM and you see 311 MB available you'd settle with that (although some probably wouldn't have bought the phone, but I digress). But the specs says 512 MB, which probably is correct, yet not quite true either. I don't like marketing bull like that, I'm sure a lot of others agree :)
[Galaxy S I9000 Android Development] Dexter_nlb:
sounds like you never heard of shared memory?

it was and in some case still is very popular on laptops, where machines comes with X GB ram, but graphics takes up 1GB alone, so windows is left with only 1GB to play with.. thats really not so uncommon as you make it sound.

it might actually be that drivers for graphics can be tweaked to take less ram, but if the memory blocks also its not one big block, it might be a problem too.
[Galaxy S I9000 Android Development] norrgrd:
About sixty at the moment, feels a lot more smooth than my previous firmware.
[Galaxy S I9000 Android Development] norrgrd:
Co Pilot Live and Google Maps (no navigation though).
[Galaxy S I9000 Android Development] xan:
Cmon...

Windows != Linux.

x86 != ARM

And still, this memory in Windows is shared, so its GPU/CPU accessible.

And yes, its still visible to the system.

Only similarity = memory taken by device driver. (In whole different way however)
[Galaxy S I9000 Android Development] lealdud1:
@norrgrd -> If you change to Norwegian locale - is gmail app translated?

I belive this is the official for scandinavia - but that other regions that get firmware released later will have a newer firmware.

Seen from a worldwide perspective, Scandinavia is a small area which Samsung don't need to focus on so much.. Therefore I think they "rush" out a -OK- firmware for us, and focus on the other regions...

And I can't belive how many people *****ing about so many things and ask the same questions over and over. Maybe this isn't the official on the other side of the world, but why can't it be in Scandinavia? Jelous?

Thanks allot for sharing info with us OP - too bad you don't have root and can share :p
[Galaxy S I9000 Android Development] Prankey:
If this would have been an official firmware, the name should suggest. I don't believe such name as JPH, JP4 (used for test releases) would be used on an official firmware. Samsung should atleast change it to something like JI2.
[Galaxy S I9000 Android Development] Adevem:
can a developer mod the taskmanager to show 512 instead of 304. so people will stop *****ing, i think we're all ram-hungry.

most of us wouldn't even know what ram does but so long as we see a number close to 512 as advertised, we'll be content... for now anyway until someone find something new to ***** about.

and to those deeming this fake once you saw that market can't be excessed regarding paid apps, then please know there is a world outside of your country and some countries are not supported yet to see paid apps without a third-party app's help.

it's a bit hazy so far but if it's official, at least we have a general note. everyone's insane regarding froyo lmao.
[Galaxy S I9000 Android Development] wliu88:
is this mean the final 2.2 for i9000 will only support 304M RAM?
[Galaxy S I9000 Android Development] Adevem:
lol. :D:D:D
[Galaxy S I9000 Android Development] Billus:
I've found a way to unlock all that missing ram. My phone shows 504mb usable so HA.

/bs
[Galaxy S I9000 Android Development] lemmy_0:
this for real mate?
[Galaxy S I9000 Android Development] Schmich:
Maybe some of us cannot update and are stuck with a phone that only works properly some of the times? Which is unacceptable for the big samsung. Even worse for us who bought the phone on 12 month contact - basically if gps fix comes end of october the gps won't have worked 25% (3 out of 12 months) of the time!!!
[Galaxy S I9000 Android Development] jdrake001:
you are just kidding, right?
[Galaxy S I9000 Android Development] nandihno:
i think thats why he has /bs

LOL
[Galaxy S I9000 Android Development] andars05:
I don't want to make this thread about RAM. I do want to clarify though.

I don't think anyone expects it to say that 512MB is available. No phone has 100% of the RAM available -- all phones reserve memory for hardware and system components. We just want a reasonable amount to be available to android/user applications. 304MB? This is worse than 2.1 The N1 shows 385-415 depending on the firmware. The N1, an older phone, but advertised as having the same amount of RAM as the Galaxy S, has an additional 110MB of RAM available for applications use. Another thread showing the amount of reserved RAM for other phones proves that the Galaxy S reserves more than its fair share when compared to other phones.

For arguments sake, even if the phone shares memory with the GPU, that doesn't make Samsung's advertising suddenly ethical or fully honest.

To sum:

No one with a decent understanding expects to have 512MB fully available.

What we do expect is:

To have a reasonable amount available for android/user application use

A reasonable number may be 380-400+ range -- making it comparable to other phones
[Galaxy S I9000 Android Development] norrgrd:
I'm afraid not, it's in English. With Swedish locale it's in Swedish though.
[Galaxy S I9000 Android Development] mark78x:
Quote! ;)

When i start up my Galaxy, I have only 120mb available, where is others 100-150mb(512mb - 250mb(for example) for system, radio, application system...)? Is shared with GPU?

Sorry for the question(and my english:rolleyes:), but i would like understand.
[Galaxy S I9000 Android Development] banttu:
I have just 1 question does the data connection work?

My JPK is showing that the data connection is in use but it doesn't work at all.
[Galaxy S I9000 Android Development] norrgrd:
Everything works just fine, including data connection (getting about 5 Mbit).

The only thing I've noticed working a tad bit worse is the reception. For example in my home there are some spots where I used to have 80-100 % reception whereas I now have 0-20 %. In areas where I normally have good reception I've noticed no difference.
[Galaxy S I9000 Android Development] Kur0saki:
How is the batterylife, do you feel it's improved?
[Galaxy S I9000 Android Development] huxflux2003:
You are all out of topic. There is a separate thread about the ram issue.
[Galaxy S I9000 Android Development] igniztion:
Let's say that the phone has 512MB RAM.

The free command (used in console/shell) tells us that around 325MB of this RAM is available to user applications. (This number varies between firmwares. Some report as little as 304MB available)

Of these 325MB, user applications are using 200MB, so that leaves you with 125MB unused, free RAM. This is what your 120mb is.

The discussion about RAM is not regarding these 325MB for user applications, it's about the difference between 512MB and 325MB. Other phones reserve around 100MB for System, radio, GPU etc, while our phone reserves up to more than 200MB.

My guess is that since we have a GPU in our phone that is quite a bit better than most other phones, it requires more dedicated RAM and this is where the larger part of our "missing" RAM is allocated.

I won't go into the blame game against Samsung here. I've never had any problems caused by low memory on my device, so I simply don't care.
[Galaxy S I9000 Android Development] Donald Nice:
Thx igniztion for your explanation. I hope this will end this ram-discussion, can we please go back to topic now?
[Galaxy S I9000 Android Development] norrgrd:
Hard to tell from only using it one day.
[Galaxy S I9000 Android Development] ntomi:
I heard that the compass was not accurate in older firmware builds (including 2.1), can you tell us if its accurate or not? OR it just needs calibration (read on other threads). Thanks
[Galaxy S I9000 Android Development] pharaohdk:
you might aswell close this thread, since you have been told how to do a dump, but also that you wont be able to since it requires root, and since you cant flash the kernal youself its pointless.

good to hear that it seems to be a final release and such. but thats about it.
[Galaxy S I9000 Android Development] norrgrd:
I was thinking about someone in my area experienced enough to figure out how to root it could help out with that.

If a mod would like to close the thread go ahead.
[Galaxy S I9000 Android Development] isaacrg1974:
norrgrd, when you release your firmware Froyo us and we will end and make all this circus to set up anything that maybe it just needed a little company or speak. Of all the ways it is true what you say you have, thanks. Lords Froy is right around the street.

God
[Galaxy S I9000 Android Development] Bec07:
Can somebody please provide swype:

/system/app/Swype.apk

/system/app/Swype.odex

/system/lib/libSwypeCore.so

Thank you very much!
[Galaxy S I9000 Android Development] exadeci:
Why this supposedly final fw has a older build date if we compare with JPK ?? I mean if this one is final JPK should be final and improved, right ? Or differents Samsung teams don't communicate ?
[Galaxy S I9000 Android Development] stuclark:
It's a pity that everyone who's b1tching about build dates / version numbers / RAM size doesn't understand how software development works!

Yes, JPK comes from a newer TRUNK revision than JPH, but that doesn't mean JPH isn't newer than JPK. If you don't understand then maybe this will help:

JP
l
l
----JPH <- JPH branched = pre beta
l l
l ----JPH <- JPH (2) bug fix = beta
l l
----JPK l <- JPK branched = pre beta
l l l
l l ----JPH <- JPH (3) bug fix = release candidate
l l l
l l
l l
l JPH <- JPH (4) bug fix = possible release code

Now, can we please stop saying JPH is older than JPK! We simply don't know the internal build dates of everything OR have the changelogs, so we can't check!
[Galaxy S I9000 Android Development] belmethos:
For those *****ing about free RAM, please read this and get a grasp of linux memory usage;

(I am sorry i can't give the link properly)

forums.gentoo.org/viewtopic.php?t=175419
[Galaxy S I9000 Android Development] norrgrd:
See first post.
[Galaxy S I9000 Android Development] bilboa1:
growing tired of "samsung fans" (i hate using that term:p) pasting random links not knowing a single bit of what they're talking about. it's just spreading disinformation :( please refrain doing that.

sure the gentoo topic is alright but it has strictly nothing to do with the memory "issue" of the sgs that people complain about, even thus it's been explained in these forums. (i'm actually a long time gentoo dev since i suppose i've to add some credentials for the (not so) credulous minds over there)
[Galaxy S I9000 Android Development] K4P1:
Just realized that all firmware JPx are version 2.2 (in all areas).

So JP branch is newest (beta or final branch?).

And because we don't know the internal build structure, all these discussions about which is newer is mostly based on build dates.

Do we really know that the build date is same as branch (internal/public) release date? (it should be near it, but who knows).

And how much does some build have code/fix from other branch?

Too many open questions.

IMO looking just build dates and version information doesn't give true information about it's state and what is "newest" or "best" build.

Later builds could be versions for some functionality tests (even for versions after froyo) and those previouse could be "stable" releases - or vice versa.

Hope you know what I mean :)

Time will tell (hopefully):rolleyes:
[Galaxy S I9000 Android Development] dewimagica:
Well its good to involve people in this discussion and entertain them till the final release goes public.

LoL !!

Why dont everyone understands that even the initial Froyo Public release could be unstable or lacking features as of Eclair's initial release.

Question is "Do we need a Froyo release or a stable and feature efficient firmware" ?

As time will go releases will come and we will see improvements..

i guess the culprit is "curiosity" which keeps us awake....

Have Fun discussing the infinity ...... ;)
[Galaxy S I9000 Android Development] mbr01:
Well, look at the galaxy Tab. Same hardware (supposedly) and this device does show more memory than our Galaxy S. Can't really explain that with the linked page.
[Galaxy S I9000 Android Development] belmethos:
Which one is important;

* show more available memory, run laggy?

* show less memory, run smooth?

Please don't get me wrong but i find these comments irrelevant, and MS windows based habits.

Edit: Are we refering the available free memory, total memory of the device?
[Galaxy S I9000 Android Development] norrgrd:
I can vouch that the Galaxy S is a lot smoother than the Galaxy Tab.
[Galaxy S I9000 Android Development] Donald Nice:
Please guys... Lets get back to topic!!!

If you want to discuss about the ram, go here: http://xdaforums.com/showthread.php?t=792512
[Galaxy S I9000 Android Development] belmethos:
Lol , your are right Donald :D. Got lost in RAM again. So there is no way norrgrd can dump his firmware? . We will wait to see if your firmware is the one when offical one is announced...:D
[Galaxy S I9000 Android Development] AyeGee:
I dont see why Samsung doesnt just release it here on xda-developers. They would have lots of free beta testers =P
[Galaxy S I9000 Android Development] K4P1:
I am trying to replace Swype, but...

In /system partition there ise only about 400k free space and new Swype files are about 5M bigger than original - so can't copy/replace those.:(

What can I do?:confused:

Are there any .apk -files I can delete in /system/app -folder or maybe other solution?

edit: Solved. I deleted (but first made backup of those) "aldiko-standard-1.2.6.1-samsung-s1.apk" and "install_flash_player.apk" -files in /system/app -folder and those gave me some 7M free space. Then I replaced "Swype.apk" and "libSwypeCore.so" -files. I deleted the odex -file (I made backup of all original files). After rebooting swype works well.
[Galaxy S I9000 Android Development] stuclark:
Of course its not the same hardware, it's got a bigger screen, different screen technology, and therefore different screen controller silicon. (and that's simply what I can think of from the top of my head)

...what you really mean is: "It's got similar specifications for processor, memory (RAM & SD) and cellular access."

It's clearly not the same hardware, but from the software perspective, it does seem interesting that the kernel / build of Android on the Tab can "see" the "whole" 512MB whereas the S only "sees" ~380MB.

...of course, none of this means the S doesn't actually USE all it's 512MB, but hey ho...
[Galaxy S I9000 Android Development] spyrale:
Fact is that sgs shows less memory and runs laggy without lagfix and taskiller. Ms habit? What are you talking about? Sgs is the only android phone with 512 mb that has this weird ram management...if you are happy with that doesn't mean that everybody must agree with you. Others say that people who complain about lack of ram are just hungry about numbers...yeah, you know what? Try to eat some number for dinner, let's see if you are satisfied with that. I think not, do you know why? It's simple, still you don't get it, problem is not numbers showed.

Sorry for Ot...and for my awful english:-)
[Galaxy S I9000 Android Development] borchgrevink:
And where is this screen shot stored? Thanks
[Galaxy S I9000 Android Development] belmethos:
Are you working for Microsoft or something? Cool down man...

I am trying to stop talking about RAM, but do you have the official froyo yet? and have you seen how it performs with the same amount of RAM? Even beta 2.2 performing better than eclair, have they given more RAM to you ? Does lag fixes do the memory management?

I stop here, about discussing RAM please do not write to this post if you want to discuss further, let's use the RAM thread instead...
[Galaxy S I9000 Android Development] Rickstur:
In your gallery
[Galaxy S I9000 Android Development] lorenzo.themax92:
please talk about the ram in this thread!!

http://xdaforums.com/showthread.php?t=792512
[Galaxy S I9000 Android Development] borchgrevink:
Hmm,does not work.... Correct is to press "back" and then "menu" on phone without any cable connections? Need root?
[Galaxy S I9000 Android Development] Rickstur:
No need for root, but the correct is: keep holding back button and then hit menu button (this is the hardware button in the middle).
[Galaxy S I9000 Android Development] 3rdcoast:
good grief you guys are having a geekasm. I think you got some on my keyboard, ewww. If this is final then I'll anxiously await it via keis or however it gets delivered by Sammy. I can wait another few weeks if I have to but it is entertaining to watch all this excitement over something that will be official soon enough. Well not exactly soon enough because I won't like this slab of crap until Sammy fixes what's wrong but I'm not going to risk another brick on a rumor on the off chance that I might get it a week before it's official.
[Galaxy S I9000 Android Development] CLShortFuse:
can you pull the GPS files?

adb pull /system/etc/jupiter.xml

adb pull /system/etc/gps.conf

adb pull /system/bin/gpsd/glgps_samsungJupiter

adb pull /system/lib/libgps.so

and zip them please? :)
[Galaxy S I9000 Android Development] huxflux2003:
So, any progress dumping this and making it available to all of us thirsty flashers???
[Galaxy S I9000 Android Development] xan:
To cut this all... I suggest dumping kernel image, TW launcher and comparing checksums with leaked JPH.

I bet they are the same.
[Galaxy S I9000 Android Development] norrgrd:
If I find a MicroUSB cable sure, otherwise I'll do it tomorrow.

EDIT: Here you go.
[Galaxy S I9000 Android Development] norrgrd:
Afraid not. I still need someone to help me out.
[Galaxy S I9000 Android Development] Qazz~:
If this truly is a 1:1 copy why havent they released it...
[Galaxy S I9000 Android Development] huxflux2003:
I am sure that are lots of ppl here willing to help you. The process is pretty straightforward anyway. Unfortunately, I have never dumped a ROM and I cannot help.

Anyone???????
[Galaxy S I9000 Android Development] CLShortFuse:
NICE!!! I also need

/system/lib/libsecgps.so

/sys/class/sec/gps/GPS_PWR_EN/value (probably just 1byte)

/sys/class/sec/gps/GPS_nRST/value (probably just 1byte)

and

if these exist

/system/bin/agpsd

/data/HALGPS_conf.cfg

/data/gps/secgps.conf

/system/libclientgps.so
[Galaxy S I9000 Android Development] norrgrd:
/system/lib/libsecgps.so attached in rar as libsecgps.so

GPS_PWR_EN/value attached in rar as PWR_EN_value (value was 0)

GPS_nRST/value attached in rar as nRST_value (value was 1)

/system/bin/agpsd missing

/data/HALGPS_conf.cfg missing

/data/gps/secgps.conf no permission

/system/libclientgps.so missing