yashsingh1/xdaforums huggingface dataset:
[HTC Aria General] ioft:
The only thing I miss from my Nokia's (N95, N82, N96, N97... yes I was a fanboy) is the camera. Nokia was notorious for memory being horrid but I got so used to it... I just WISH they would adopt Android and continue to make phenomenal hardware... I was waiting so long for the N8 to come out (I settled with the N82) and I just got tired of waiting. They announced the phone so long ago and I think it finally started shipping a couple weeks ago... one of their biggest downfalls that never changed when they had all their internal blowups. I do miss Symbian... but I've been using *nix for 10 years now and am far more comfortable with that than Symbian... and change is sometimes good. I'll wait until their next true flagship model is released and see what happens...
[Galaxy S I9000 Q&A, Help & Troubleshooting] xmodpt:
Hello all...

1st of all good work on all FW´s that come out from this site ...:D:D:D

now my problem.

I just got a brand new Galaxy S, and i need your help to see if the problem is me or the phone.

Problem 1:

When ever i put the phone to charge, it get so hot on the speaker that you cant put it next to your ear.

I got my self a new charger.... same thing... new USB cable... same thing.

I have changed the FW to JPK´s FW with droid 2.2 froyo.

Problem 2:

they sell this phone as a phone 4 internet use, but if i use it.. the battery runs dry in about 40 min...

Question:

- has any of you had the same problem ?

- does it have anything to do with the FW upgrade ?

I think it´s a hardware problem but i just whant to be sure.

Thank´s 4 all your help.

Nuno
[Galaxy S I9000 Q&A, Help & Troubleshooting] webstar1:
If u use the phone when its on the charger then yes it does get warm

And the battery might of been wasted because of some app your using, I was using a custom lockscreen and it drained 50% of my battery in 10 min, YES 10 min.

Try XXJPM with darkkys steel

My galaxy s is good with that
[Galaxy S I9000 Q&A, Help & Troubleshooting] Deedend:
I have a Galaxy S GT-I9000 and I don't have this problems, with stock firmware I navigate for 2 or 3 hours without run dry all the battery.. maybe it's a battery issue of your phone.
[Galaxy S I9000 Q&A, Help & Troubleshooting] Ladduro:
+1 same here
[Galaxy S I9000 Q&A, Help & Troubleshooting] Ganfas:
from you problem 1 + problem 2 i would say that's a problem with the battery. But it's only an opinion
[Galaxy S I9000 Q&A, Help & Troubleshooting] xmodpt:
Thank 4 the int but the 1st thing i did was to un-install all aps but the prob is still there.

regarding calls, that i know but the thing is... get to hot just charging.

thnk m8... i will give it a try.
[Galaxy S I9000 Q&A, Help & Troubleshooting] shad0w1989:
Regarding the battery problem,

keep in mind that youre phone is brand new. AFAIK all batteries need a few cycles of loading to get their full capacity. In the first two weeks my sgs didn't make it through the whole day of usage, whereas now it has about 60% at the end of the day (Nighttime = Loading. Usagetime without or very little charging (when i plug it in @work to listen music = 08:00 AM - 11:30 PM)

(Sorry for my bad english)
[Galaxy S I9000 Q&A, Help & Troubleshooting] xmodpt:
mmmm could be that.

What FW do you guys use ? and how do i install it ....

Thnkx
[Galaxy S I9000 Android Development] ykkfive:
just performed some tests with different reserved mem sizes (stock kernel ZSJP8) for your ref

default settings:

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=16384

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=10240

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=14336

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=36864

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=36864

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=5012

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240

1/. minimum (almost) reserved mem with movie playback possible (no lag in youtube), 356mb memory, no special lags observed, opened 4 tabs in browser with lots of imgs and swfs

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=8192

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=6144

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=6144

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=29696**##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=29696**##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=3072

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=2048

** min value in order to play movies = 29mb, 28mb wont play

## can be set to a lower value without movie playback, setting these with too low values caused problems, below 20mb should be ok

2/. nearly double all default values, 219mb available, didnt feel faster

EDIT 201010271843HKT: tweaking memory test2

available memory - 257.68mb

EDIT 201010280000HKT:

as to min mem usage, u'll need to (in brief):

1/. remove unneccessary apps

2/. remove startup/network chg broadcast listeners from the app - a lot of apps/services are launched at startup up or network state chg, remove them so they wont start automatically, eg gtalk, sync/feed, vold service, installd, etc

3/. kill unneccessary services & processes - i didnt use any killer since i rooted my phone, i use script to kill them since killers consume more mem

4/. i have read the source and found that only -Xmx (max mem) is included but no -Xms (initial mem), perhaps we can do something here (not done yet)

reference for 2.1 http://xdaforums.com/showpost.php?p=8507031&postcount=38
[Galaxy S I9000 Android Development] xos84292:
It 's very useful info! thanks your test!
[Galaxy S I9000 Android Development] mengsuan:
Can I have a guide to make these changes to my existing kernel?
[Galaxy S I9000 Android Development] EarlZ:
Nice, able to see 356MB instead of 304!
[Galaxy S I9000 Android Development] xos84292:
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=8192

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=6144

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=8192

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=8192

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720**##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720**##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=4096

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=5012

can make one kernel for this setting? i want to test,but i don't know how to make a zimage.
[Galaxy S I9000 Android Development] jam3sjam3s:
These results exclude the 'blackholed' memory, right? Which means if we can find where it is used (if it is used at all) we can get even more?
[Galaxy S I9000 Android Development] hardcore:
Great work there. Could gain us a couple more MB of usable RAM.

The "48MB hole" is most likely used by the GSM Radio and we won't have access to it.
[Galaxy S I9000 Android Development] ykkfive:
i'm sorry, my kernel will restart once the usb cable is unplugged, still looking for a solution....
[Galaxy S I9000 Android Development] ykkfive:
what blackhole r u talking about?
[Galaxy S I9000 Android Development] andars05:
This is awesome! I can't wait to see a kernel with the resolved usb issue and more ram.
[Galaxy S I9000 Android Development] ed10000:
Yay! Finally we have experts working on the RAM issues! :)

BTW, is there no way to allocate memory dynamically for all these things as and when it is needed instead of reserving a set amount? Especially for the video playback stuff, it's a lot of wasted memory when you're not playing a movie / doing something graphic intensive. :(
[Galaxy S I9000 Android Development] halabibk:
Can anyone explain how to do a safe changes of this paremeters.....?

Thanks
[Galaxy S I9000 Android Development] xan:
Try 720p video capturing, encoding is hardware accelerated as well. (but might not be affected by those settings, it just needs checking)

Yes, dynamic allocation would be awesome :)

Those settings are accessible in source code = before compilation, so no way to change them post-startup/post-compilation ATM.

How come u got only around 100MB memory used?

I got over 140 just after startup..
[Galaxy S I9000 Android Development] sztupy:
This is still not 512MB as samsung promissed us! I hate this phone! I'll buy a Desire Ultra HD as soon as it's annoucned!

(just to be the first troll in this topic :) )

nice work though!
[Galaxy S I9000 Android Development] andars05:
I don't think that the argument ever was that Samsung promised 512MB of usable RAM. It was that the amount of RAM usable out of 512MB for applications was not comparable to other phones with 512MB.

I don't want this to turn into an argument. I'm just glad that the problem is coming to fruition.
[Galaxy S I9000 Android Development] dupel:
You clearly either have no sense of humor or cant read :rolleyes:
[Galaxy S I9000 Android Development] andars05:
I know it was sarcastic. He was making fun of the people who wanted more RAM. I was just stating that no one (with exception of a few maybe) expected 512MB of RAM to be fully usuable. I think he misunderstood the original issue :)

I believe the issue was largely ignored because of this misunderstanding. It didn't help that people who expressed dissatisfaction were told to "stfu." A good portion of people were unhappy with the amount of available RAM. It wasn't that they expected to have full access to all 512MB.

I'm happy to see progress on this issue.
[Galaxy S I9000 Android Development] SupaDuckie:
How are we able to change theSe values???
[Galaxy S I9000 Android Development] mengsuan:
Any kind souls?
[Galaxy S I9000 Android Development] dupel:
How about reading? Its just freakin 2 pages, not 50...
[Galaxy S I9000 Android Development] INeedYourHelp:
I tried both. Version A is a lot better for me. Things open faster with it and it just feels smoother.
[Galaxy S I9000 Android Development] d3885u:
@hardcore...

I must admit that your latest modded kernel (version B) is just amazing...

The fastest kernel I've ever used before...Thanks for your great job...
[Galaxy S I9000 Android Development] hardcore:
Sometimes I wonder the difference between compiler options is mostly placebo!

But one thing for sure ver c and d give another 1 to 2mb ram free because the kernel is smaller. :)
[Galaxy S I9000 Android Development] vanahaim:
@hardcore

Would not it be better to start a new topic for your work? For clarity etc..

PS Version D has no problems for me.
[Galaxy S I9000 Android Development] sunwee:
hardcore, great job on your optimised kernels. this is one thread i'll be following closely.

one question, as i understand, since this is based on sztupy's kernel, it should be working for jpm/jp9 roms. but i am liking doc rambone's rom as well, which the latest one is based on JPA.

so the question, can this kernel work on JPA as well?
[Galaxy S I9000 Android Development] hardcore:
I'm not sure, but I think jpa jpm jp6 are using the same or similar kernel. If there's any risk it would be in compatibility of the lagfix or startup scripts.
[Galaxy S I9000 Android Development] hardcore:
Good idea. I also wanna share the jhash speedup.

Will do later once we've settled on a safe ram configuration. Right now we seem to make more progress discussing ram issues in this thread.
[Galaxy S I9000 Android Development] ykkfive:
No problem. Will post a sample later
[Galaxy S I9000 Android Development] moreira86:
so, i already flashed the first 341mb kernel, then applied lagfix from doc rom, so in order to flash the new kernel from here should i disabled the lagfix, flash kernel, then re-apply it?
[Galaxy S I9000 Android Development] dupel:
Why did you swithc O3-2-s (what s means?) I think I preffered speed with O3 enabled. And I think I can compromise that 1-2 mb of ram for a bit of speed (if the intention was to gain ram but compromise a bit of speed) =)
[Galaxy S I9000 Android Development] dupel:
If its docs rom (and you use universal lagfix, not voodoo (have to manually flash it)) than just flash kernel.
[Galaxy S I9000 Android Development] c010:
tested B, C & D, gallery is not working, camera is not working too
[Galaxy S I9000 Android Development] hardcore:
Agreed on your thoughts if we gain a bit of speed.

But the thing is, it's not so straightforward, and I'm not sure if O3 is really faster than O2 or even Os. But O3 produces code that is bigger and takes more RAM, so it may actually be slower if it cannot fit in the cache.

They all benchmark about the same, which makes it even harder to tell.

The recommended setting is O2, but no harm trying a few settings to see if there are any differences (besides the size). Here is one article that suggests options for compiling the kernel for Gentoo:

http://www.gentoo.org/doc/en/gcc-optimization.xml
[Galaxy S I9000 Android Development] hardcore:
It should work. It works for me at least. Maybe your /system or /data or /dbdata got corrupted somehow.
[Galaxy S I9000 Android Development] tommy34:
works for me too, no problems so far on D
[Galaxy S I9000 Android Development] Pilotxxx:
What is the best version? B C or D?
[Galaxy S I9000 Android Development] EarlZ:
Same question here, currently Im on B
[Galaxy S I9000 Android Development] xan:
U guys played with menuconfig? There are fpu related options there :)
[Galaxy S I9000 Android Development] specialex:
maybe media scanner still running, so cant open the camera
[Galaxy S I9000 Android Development] c010:
Unfortunately that is the not case. Perhaps i should reflash everything from scratch again.
[Galaxy S I9000 Android Development] d3885u:
Hello gan...wkwkwkwkwk...

Which version is the best for you?

I haven't try the C and D version from hardcore...but now I'm running the B version and everything is just fine for me...and I feel battery improvement working so well on B version

Sent from my Galaxy S
[Galaxy S I9000 Android Development] herly:
Anyone has already tried with JP6?
[Galaxy S I9000 Android Development] d3885u:
Loh...how are you gan?

Is it "kaskus in english version"?

Hahahaha...

@hardcore

Why do you recommend O2 version over the Os and the other?

Speed-wise, which one is fastest between O2 and Os?

Sent from my Galaxy S
[Galaxy S I9000 Android Development] hippo_potamus:
2.6.29 for Eclair

Hi,

Anyone know if it'll work on 2.6.29 for Eclair?
[Galaxy S I9000 Android Development] Ettepetje:
The kernels mentioned here are variations on: [KERNEL][101022] Universal lagfix [EXT4,JFS] and tweak kernel [BLN] {0.3}. Made for JPM/JP6/"Multinational 3.0 ROM" (all these are froyo, so NO, not Eclair).
[Galaxy S I9000 Android Development] herly:
Gr8 gan ....

Just want to try this for my JP6, like I'll be the first ... :D

@hardcore

Thanks for your awesome work ....
[Galaxy S I9000 Android Development] hardcore:
I'm not sure myself. O2 is standard, Os in theory might be slower but smaller code. I'm trying Os to see if it feels slower in real life usage or not. In BenchmarkPi and Linpack they benchmark about the same.
[Galaxy S I9000 Android Development] INeedYourHelp:
O3 felt smoother for me compared to O2 ;)

I hope you continue to release O3 versions of your great kernals.
[Galaxy S I9000 Android Development] android.francis:
i have JPM and currently have VOODOO 5 pre6. Would I need to disable Voodoo to test this new kernel? Also, Once I install this, can I re-enable voodoo?
[Galaxy S I9000 Android Development] captive:
You MUST disable voodoo!

You can eventually enable whatever lagfix you want from the modded recovery available with this kernel (ie: reboot in recovery, go to ULF options and choose you lagfix scheme, then just reboot)
[Galaxy S I9000 Android Development] herly:
Apply D version with JP6 just now .... awesome ... more responsive .....
[Galaxy S I9000 Android Development] zenkinz:
there's actually no need to disable voodoo.

but one must go into the cwm recovery mode to enable/disable the lagfix, so that the partitions are properly format/configured for use. otherwise, w/o doing so and just flashing the universal kernel over voodoo kernel, will probably end up with a boot failure.
[Galaxy S I9000 Android Development] android.francis:
unfortunately, cwm is not avalailble for voodoo 5 pre6.
[Galaxy S I9000 Android Development] zenkinz:
once you flash this kernel, it'll have.
[Galaxy S I9000 Android Development] vanahaim:
@ hardcore

It would be nice to see the OC version!

With elements from

http://xdaforums.com/showthread.php?t=821514

or

http://xdaforums.com/showthread.php?t=822027
[Galaxy S I9000 Android Development] herly:
FYI ...

On my testing with JP6, D version more fast than B ...
[Galaxy S I9000 Android Development] android.francis:
Yes, you are correct with that one. I installed B over voodoo 5 pre6. also enabled Voodoo in cwm.

I now have a bit of lag when I use my phone compared to when I was just using voodoo 5.

Strange.
[Galaxy S I9000 Android Development] zenkinz:
in theory, once you have the lagfix enabled & configured (i.e. partition format accordingly), it shouldn't matter if you are on voodoo or the ulk kernel. but supercurio might use different compiling option when building the kernel image but I would expect better performing from the memory tweak kernel instead.
[Galaxy S I9000 Android Development] hardcore:
Maybe its because of the HZ value. In these kernels I've lowered the HZ value to 100 (default is 256), hoping that we can get better battery life. But it might make the UI a bit more jerky. I'd appreciate any feedback on battery life with these HZ=100 kernels.

I'm also trying now with HZ=200 to see if there is any difference.

BTW, I once flashed ULF directly over a Voodoo-converted /data partition, and it worked. But that's just me - better to do a backup first in case you lose /data or /dbdata.
[Galaxy S I9000 Android Development] powerdams:
I test the D version with JPM, thanks for your hard work !

Noob question (sorry for that) :

-Dynticks in tickless mode still use HZ, right ?

-Do you think the UI will be more responsiveness with Higher HZ, like 500 or 1000 ?
[Galaxy S I9000 Android Development] lokhor:
Is it possible to have a swap partition on the internal sd or would this decrease performance?
[Galaxy S I9000 Android Development] sztupy:
Both ULTK and Voodoo do an autodetect at the first start, so they'll work. Problems might rise if you do an ULTK->Voodoo->ULTK, or Voodoo->ULTK->Voodoo switch, as both might store some data about the results of this autodetect that can mean problems. (You can also switch from ULTK to Voodoo if you only converted /data to ext4, or /data and /dbdata for newer voodoo versions)
[Galaxy S I9000 Android Development] sztupy:
because of sync issues: yes
[Galaxy S I9000 Android Development] INeedYourHelp:
hardcore, is -mthumb simply to reduce code size or does it have any performance effects?

(I tried googling and all i got was mention of reduce code size).

I ask because I am deciding which O3 version to use -

First version had no enchantments at all

Second version had neon enchantments

Third version (version A) simply had -mthumb (i am currently using this one)

(luckily i downloaded them before you removed them)
[Galaxy S I9000 Android Development] madmack:
anyone tried any of these kernels on JPA ? do they work ?
[Galaxy S I9000 Android Development] darkstar2k77:
Thanks, Hardcore.

+1 hardcore's kernel version D. My phone is working like it should now.
[Galaxy S I9000 Android Development] hardcore:
It depends, sometimes mthumb might be faster or slower.

But I think the code has to properly support compiling the kernel in thumb2. From what I tried, this toolchain doesnt really support compiling the kernel in thumb2 mode yet - I changed the kernel CONFIG_THUMB2_KERNEL but make threw an error. And subjectively, I feel that the mthumb version feels a bit less smooth. So, I think its better to build it in arm code (without mthumb) now.

Also, I'm trying O2 with some other optimization (from what I've read, O3 may be slower than O2 for the cortex-a8 CPU). But I'll throw up an O3 version too, just so we can test a few.
[Galaxy S I9000 Android Development] vanahaim:
@hardcore

Are you thinking about OC version? ;)
[Galaxy S I9000 Android Development] moreira86:
yea. i would like to see the 341mb with oc, would be nice :)
[Galaxy S I9000 Android Development] android.francis:
There another thread by hardcore regarding RAM, is that what we should be monitoring from now on?

Anyways, I just wanted to share my 2 cents with version D. I first tried Dark Steel ROM but had some issues with Market so I flashed back to JM8, then flashed to JPM. I then installed Voodoo 5 pre6 then flashed hardcore's version D without disabling anything.

After the last reboot, I was not taken to recovery or anything and my phone is working fine. I'm still testing it by using all the pre installed apps and also DL and using apps in the market.

So far, so good!

Job Good hardcore! :)

Update: there seems to be 2 new FROYO out there. Once the dust settles a bit, I'll test this baby on one of those.
[Galaxy S I9000 Android Development] mengsuan:
I posted in page 1 to ask for help.
[Galaxy S I9000 Android Development] ykkfive:
just modify .config and recompile the kernel
[Galaxy S I9000 Android Development] EarlZ:
Not everyone here knows how to do that, can you provide steps ?
[Galaxy S I9000 Android Development] ykkfive:
well, as mentioned in earlier post, my phone reboots with any modded kernel if the usb cable is not plugged in, and i'm still looking in this problem.
[Galaxy S I9000 Android Development] RyanZA:
It's not really that easy, I'm afraid. There are no 'regular person friendly' guides for building up your own SGS kernel either. Hopefully a kernel pro can put up a nice easy to follow guide at some point. :D I did manage to do it with a lot of guess work.. but it's not pretty, or optimized. Maybe one of the optimized kernel pro's around here could help us all out with a guide? :D
[Galaxy S I9000 Android Development] Tayutama:
You aren't alone in that one Ryan :)

Got a kernel built myself but got the same problem as ykk_five has :(
[Galaxy S I9000 Android Development] ykkfive:
u also?

actually i didnt know that for a few hrs coz the usb's plugged in all the time for the adb and debugging
[Galaxy S I9000 Android Development] Tayutama:
Actually i didn't have my phone connected to usb before when i tested my kernel and it was just rebooting like crazy.

Didn't try with usb in before i read what yours was doing and it boots just fine when usb is in now.. but else reboots :(
[Galaxy S I9000 Android Development] s88:
my friend bought a p500, and the phone memory available after boot is 247MB..

as a result, the phone is very responsive and app startup is fast with no visible lag, even though it is running on a slower processor and limited internal phone memory.

If only galaxy S has so much memory.....
[Galaxy S I9000 Android Development] RyanZA:
Umm.. RAM has nothing to do with responsive and app startup - that is the filesystem. Try out z4mod if you're courageous or OCLF or Voodoo if you're less so, and your phone should be very responsive and apps open instantly.

Here is a video of z4mod: http://www.youtube.com/watch?v=rXINc9zse-0&feature=player_embedded

More RAM is so that we can have more apps open at once for better multitasking...
[Galaxy S I9000 Android Development] s88:
Galaxy S still need autokiller/minfree to optimize the memory setting
[Galaxy S I9000 Android Development] hardcore:
Actually, with the latest roms and some of the speedup hacks, I don't need to increase the minfree settings anymore. The Samsung defaults are actually somewhat aggressive.
[Galaxy S I9000 Android Development] DSF:
Instantly?

People what's wrong with your sense of feel?

That's not instantly. Look at facebook app. Look at music app. Also, you don't know what apps were already loaded (contacts & dialer were already opened)

And RAM does MATTER here. If you are below 50 MB the is so laggy. +++
[Galaxy S I9000 Android Development] FadeFx:
i think the phone actually gets unresponsive if free ram falls below vm-heapsize that is 48mb so it can not allocate the full heap size and has to free up something first. however, in froyo i never had to change the minfree settings in any way.
[Galaxy S I9000 Android Development] sztupy:
Here is a compiled kernel with the modified settings: http://xdaforums.com/showpost.php?p=8791495&postcount=26