yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] halabibk:
Hi sztupy, the kernel is working fine but so far I found a bug that you can't write the external_sd.
[Galaxy S I9000 Android Development] hardcore:
The default minfree settings try to keep free ram above 48mb already. If your free ram drops below 40mb or so it means something's not right, maybe a memory leak in some app.
[Galaxy S I9000 Android Development] sunwee:
great!

pros: launcher pro seems to stop crashing after coming back from an intensive app, browser seems smoother, overall usage seems smoother as well.

cons: camera can't record 720p (fc), video player also can't play 720p (error message: Sorry, this video cannot be played)

can the settings be tweaked further? maybe a bit less ram?
[Galaxy S I9000 Android Development] ykkfive:
o.. i didnt try to record nor play 720p videos, just tested with youtube HD only

if u need that u'll have to increase the values
[Galaxy S I9000 Android Development] sztupy:
Yes they can probably. One has to try though.
[Galaxy S I9000 Android Development] matthewtse:
besides the 720p video problem, i found that 3g video call doesn't work too.

just after the call is connected, the phone just reboot.
[Galaxy S I9000 Android Development] FadeFx:
works for me...

edit: uups, didnt realize it was about video calls...

didnt test them, because i am not interested.
[Galaxy S I9000 Android Development] jeebspawnshop:
Dunno if this helps, but seeing as the Galaxy Tab is basically a giant Galaxy S, they both pretty much run the same stuff in terms of hardware and software.

But the Galaxy Tab shows 444MB of free RAM in the RAM Manager, and the Galaxy S shows, well, what you already know...

I know I'm not helping out much here, LoL, but every little helps I guess ;) Perhaps someday someone can figure out what the SGS is doing wrong and what the Tab is doing right.
[Galaxy S I9000 Android Development] hardcore:
The Galaxy Tab uses lower values for some of those settings than the Galaxy S. A good place to start for a 'safe' lower setting might be to compare the Galaxy S and Tab values, and use the lower of the two. Might not get us the extra 50MB or so, but might be able to get a few MB out of it, or at least lead us in the direction of which settings are safer to set lower.
[Galaxy S I9000 Android Development] DamianGto:
Well it has more ram the sgs.

Sent from GT-I9000 Jpm OS kernel with z4mod
[Galaxy S I9000 Android Development] jeebspawnshop:
According to every source I can find out there, the Tab has 512MB RAM, just like the SGS.

And if there are any logs or non-invasive terminal commands / readouts I can execute on my Tab to possibly help you devs out, lemme know ;)

I can't get too fancy with it, as I now do a lot of my work on the Tab so I can't risk it getting botched. I use my SGS for experiments now :P
[Galaxy S I9000 Android Development] andars05:
I believe they found out that upon teardown that the Tab actually has more than 512MB. Where the Galaxy phone has a 128MB module, the Tab has a 256MB module (there are other modules that combine). I'm sure someone can clarify further.
[Galaxy S I9000 Android Development] Idan73:
That's the thing tab has 512 ddram and galaxy s a lot less plus some other kind (forgot the type now) to make it false advertised 512. But finding values from tab should be usefull.
[Galaxy S I9000 Android Development] clubtech:
That is correct.

The Tab has more than 512MB RAM.

It has 128MB more than the SGS. there was a detailed proof for this on another post.
[Galaxy S I9000 Android Development] jeebspawnshop:
Oh snap! I just got schooled! :eek:

My offer still stands though :cool:
[Galaxy S I9000 Android Development] sztupy:
For 720p recording:

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288

Tried with 9216 for FIMC0 and FIMC2 that wasn't enough, 12288 for both seems to be enough for them, and you can record 720p video. You can't play them back though :) 344MB RAM total this way.
[Galaxy S I9000 Android Development] andars05:
Is the video playback done using hardware acceleration? Would it be possible to reserve less and make the system playback files without hardware acceleration?

If my questions are way off base, please do tell :)
[Galaxy S I9000 Android Development] dupel:
yes, what about mvideo player
[Galaxy S I9000 Android Development] sztupy:
Recording and playback works with the following config:

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=8192
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096
CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024
CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=29696
CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=29696
CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=3072
CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=2048

http://android.sztupy.hu/dl/Universal_lagfix_kernel_JPM_0.4_megaram_pre.tar

EDIT: forgot to say: 343MB total
[Galaxy S I9000 Android Development] xan:
This one seems to do the job ;D
[Galaxy S I9000 Android Development] sztupy:
3g video call is still untested. too expensive to test...
[Galaxy S I9000 Android Development] INeedYourHelp:
Well I would think that if it can do 720 video recording, then video call shouldn't be a problem, right? Video calling uses less resolution.
[Galaxy S I9000 Android Development] sztupy:
If it uses another memory territory than compression/decompression then it wouldn't work. It might also be possible that the modem firmware uses (false) information about the memory layout, and therefore it can't boot the video recording up.
[Galaxy S I9000 Android Development] EarlZ:
340MB is a decent amount compared to 304MB
[Galaxy S I9000 Android Development] pitree:
3g videocall FC and reboot. :(
[Galaxy S I9000 Android Development] LockeOn:
Is there anyway to get to 400Mb of avaliable RAM and have everything working or is it just impossible?
[Galaxy S I9000 Android Development] sztupy:
we are having problems at around 340MB too...
[Galaxy S I9000 Android Development] EarlZ:
Would 335MB be problem free?
[Galaxy S I9000 Android Development] dupel:
What i dont understand is why samsung went this idiotic way of reserving ram for certain functions. Pretty much all phones I know, as far as I know:), use ram for everything, without reservations.
[Galaxy S I9000 Android Development] sztupy:
yep, samsung's aries is one of the first ARM devices to use DISCONTIGMEM. Probably to make the media functions rock solid. (and sacrificing general usability memory space)
[Galaxy S I9000 Android Development] andars05:
Is it theoretically possible to recode the drivers so that it would not require reserving ram. I imagine this would be pretty difficult though.

340 is still a pretty big improvement!
[Galaxy S I9000 Android Development] dupel:
And failing to do so =)

Seriously, dont know if its android limitations, samsung limitations, but most phone features from calling, to playing music or taking pictures was much more consistent and enjoyable experience on my poor old 5800, which was embarrassingly slow and buggy.

On a more serious note. What would happen if we choose to use different from stock apps (video player, camera). Would they depend on reserved ram, or will they act as normal aps, not touching reserved ram?
[Galaxy S I9000 Android Development] karakake:
Just FYI, the most recent Froyo leak in Korea had 340mb of total mem space available, increased from what we had in eclair. But I doubt whether Samsung will apply it to international i9000 because they updated a native call recording fuction only to Korean variant long time ago
[Galaxy S I9000 Android Development] EarlZ:
I also hope google makes its own move to help "fix" this issue in the future.. probably have a stringent system requirements to set something like 1GB full usable to end user applications and have another set of memory for system reserve.
[Galaxy S I9000 Android Development] sztupy:
That would be more like Microsoft, and would block low-level android smartphones.
[Galaxy S I9000 Android Development] INeedYourHelp:
wait, they don't have official froyo yet? lol.
[Galaxy S I9000 Android Development] sunwee:
i tested stuzpy earlier release (356mb ram) and 720p video works with Rockplayer. so it could be a limitation to default video player only. i don't have any 3rd party recording apps to test if it could record 720p.

another thought, stuzpy 350mb release, can someone try 3g video call with 3rd party dialers (if they exist)? i feel the sgs could really do with any extra ram. the 356mb ram make a lot of difference in usability feel.
[Galaxy S I9000 Android Development] EarlZ:
They could segment it into Gingerbread 3.0 and 3.0 Lite , for the low end phones that dont meet the hardware requirements.
[Galaxy S I9000 Android Development] sztupy:
They already do that somewhat, but there are still too much differences between each categories, as they mainly differentiate them by the screen resolution (for example the SGS, nexus one and the original moto droid are both in the mid-range category)
[Galaxy S I9000 Android Development] andars05:
I wonder if it is just a limitation of the built in apps. If those apps could be replaced, or tweaked, as dupel suggests, maybe we could free up more RAM.
[Galaxy S I9000 Android Development] TheBeano:
The memory is reserved to do hardware-accelerated video decoding using the GPU. Player apps that don't include their own video codecs (everything except Rockplayer as far as I know) will all have the same problem. Rockplayer is slower and chews a lot more battery that the builtin codecs, so losing the built-in codecs is not a good tradeoff unless you don't watch or record any video at all.
[Galaxy S I9000 Android Development] andars05:
In that case, could a more efficient use of the codecs in conjunction with the hardware acceleration be used? Or is this something hardcoded into the chip (as in unchangeable by a skilled dev)?

Either way, I echo the sentiment that some form of dynamic allocation would be cool.

I also had a question regarding SPARSEMEM vs DISCONTIGMEM vs FLATMEM. Would anyone mind explaining, in somewhat basic terms, what the differences are? I tried googling, but it didn't return anything helpful. I'm not a developer, but am interested in learning/gaining a better understanding.
[Galaxy S I9000 Android Development] hardcore:
If this is true, then can we please get the dmesg output from that ROM, so that we can copy the memory config settings? Then we would know which ones can be lowered safely.
[Galaxy S I9000 Android Development] dupel:
The thing is, korean version uses different modem hardware, that might make a difference here.
[Galaxy S I9000 Android Development] mapas:
Since Samsung programmers seem to prefer lazy coding I guess (just a guess) that they hardcoded memory requirements in the drivers too...

For example they reserve 32MB for video decoder and then the video decoder just uses this space without checking what is available or how much was allocated by the kernel...

So, perhaps, modifying the kernel values will not change the values that the drivers expect to use...
[Galaxy S I9000 Android Development] BlueEyes99:
As far as I remember, we had more usable RAM in Eclair. Maybe someone could compare the Frodo RAM values with the ones in Eclair so at least we can get the same results as we had with Eclair. That would be a good start.
[Galaxy S I9000 Android Development] ykkfive:
Yes they r not the same but froyo may require more ram, just like xp vs win7
[Galaxy S I9000 Android Development] ykkfive:
I am running on 356mb, everything is ok. Browser lags not as often as before. So far i didnt c any problem

ps i don record movies
[Galaxy S I9000 Android Development] hardcore:
The reserve values we r modifying do not include the radio. It is mostly the video hardware. So it should be usable.
[Galaxy S I9000 Android Development] matthewtse:
after testing, the minimum config for 3g video call to work is...

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=8192

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=4096

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=29696

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=29696

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=3072

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=4096

based on Universal_lagfix_kernel_JPM_0.4_megaram_pre.tar,

just increase CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM from 2048 to 4096 should work!
[Galaxy S I9000 Android Development] ka2uki:
how to add into the 0.4?
[Galaxy S I9000 Android Development] sunwee:
how much ram will this config yield? can someone create a kernel for testing?
[Galaxy S I9000 Android Development] matthewtse:
341MB visible

i've used sztupy's vm to compile it, attached Universal lagfix 0.4 + the above config

you can unzip and use odin to flash as pda
[Galaxy S I9000 Android Development] ka2uki:
great!!!thanks!!
[Galaxy S I9000 Android Development] avary:
this is really cool, since i don't need 3g video call and 720p recording, i can enjoy 356MB ram :D
[Galaxy S I9000 Android Development] knanda:
Do i need to remove the root and lagfix to flash this kernel?Using Jp6
[Galaxy S I9000 Android Development] Disgustipated:
Is this Captivate friendly? Or do I need to run an i9000 ROM? Thanks. Can't wait until this is integrated into more kernels. As long as I can do 720p recording (don't care about 3g video calls) and get that extra 40~ mb of RAM, I'll be happy. One of my few complaints about the SGS is the small amount of usable RAM.
[Galaxy S I9000 Android Development] matthewtse:
if you use ultimate lagfix before, you can flash it without remove the root and lagfix.
[Galaxy S I9000 Android Development] matthewtse:
sorry...i don't know, you better ask sztupy. coz i used the vm from him to compile.

i don't know if ultimate lagfix compatible with Captivate. if it does, i believe you can use it in Captivate, otherwise...cannot.

all credit goes to sztupy.
[Galaxy S I9000 Android Development] knanda:
Removed OCLF and Root..Using recovery 2e.Can i now flash this safely??Fla
[Galaxy S I9000 Android Development] spyrale:
flashed on voodoo doctor 2.1 and...it's awesome, thanks! hd recording and reproducing works fine and phone is smooth as ever. now i have 175 mb free ram :D
[Galaxy S I9000 Android Development] ykkfive:
glad to see u guys are happy with this tweak :D
[Galaxy S I9000 Android Development] Shivatink:
pls can u explain how did u flashed that am using same rom too... shud i have to disable lagfix r something...
[Galaxy S I9000 Android Development] spyrale:
you can flash it without changing anything, just put file provided in pda in odin (without touching anything else), put your phone in download mode and flash right away...another phone will boot, seriously. this is the first time i'm totally happy with sgs. don't know if it is ram, new kernel, both, but now it flies...applications open instantly, hd recording is fine (tried 1080x720), tried different heavy games and no one single problem. now i wonder...why didn't samsung do that?? will sgs explodes? :)
[Galaxy S I9000 Android Development] el_tuba:
Yeah :) But you can't buy some brain. Device has TOTAL 512M DDR SDRAM. 1 gigabit of RAM used by kernel, some memory from userspace(3 gigabit) used by devices. I'ts embedded platform, welcome to real life :)
[Galaxy S I9000 Android Development] Lalaca:
Welcome to Sarcasm Land.

What you missed on the way: The Point.
[Galaxy S I9000 Android Development] sztupy:
Find a dev who has a captivate, and is willing to test. Unfoprtunately I don't know the current state of the captivate developments.
[Galaxy S I9000 Android Development] vinclar:
Sure Kernel uses 128MB ram? Just some facts, please Im a bit noob just wanna know more.

Phone sees 464MB, 48MB are blackholed(perhaps radio, gsm,..).

From this 464MB we are able to see 356MB

In fresh flashed rom you can see that from this 356MB we have around 106MB in use.

By default we see 304(if I'm not wrong) default settings, and memory reserved is:

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=16384 16MB

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=10240 10MB

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500 1,465MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=14336 14MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024 1MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288 12MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=36864 36MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=36864 36MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=5012 5MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240 10MB

Total reserved: 141,465MB plus total memory by default= 445,45MB

Phone sees 464MB-445.45=18.55MB for what
[Galaxy S I9000 Android Development] mapas:
Great work guys !!! 341MB :)

Lets aim for even more !
[Galaxy S I9000 Android Development] °Dexter°:
Works perfectly (no strange tasks so far,though)
[Galaxy S I9000 Android Development] K0v4L:
well, can't flash it on doc_kalpik v5.1 :/ worked fine on v5

edit: my fault, everything is ok now.
[Galaxy S I9000 Android Development] halabibk:
What happen if we compile a kernel without reserve memory,

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=16384 16MB

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=10240 10MB

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500 1,465MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=14336 14MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024 1MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288 12MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=36864 36MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=36864 36MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=5012 5MB

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240 10MB

sorry for my noob question, but I will like to try it.

Can anyone compile the kernel for me without those memory parameters...
[Galaxy S I9000 Android Development] Shammyh:
Anyone taken a look at this tear down:

http://www.phonewreck.com/2010/08/19/samsung-galaxy-s-teardown/

It would seem to show that the baseband (radio) processor is using it's own separate memory chip. So assuming that the total "512 MB" is not being used by the radio, and based on this recent work, we're beginning to know how the divide from the os/kernel/gpu works... can't we figure out where the rest is hiding (or perhaps being used)?
[Galaxy S I9000 Android Development] usli:
not working in takuyama superlite :(
[Galaxy S I9000 Android Development] d3885u:
Please try to flash to Tayutama Full/Lite Version first...

I'm using Tayutama Lite Version 1.0.2 and this Kernel works great on it..:D
[Galaxy S I9000 Android Development] dereknas:
Need to uninstall Voodoo first before installation?

Hi, I'm currently on Darky's Rom with Voodoo lagfix applied. Must I disable the lagfix first, apply this kernel and update the lagfix again or I can just apply it over the lagfix?

Thanks.
[Galaxy S I9000 Android Development] vinclar:
This report seems wrong, it shows only a 1Gbit(128MB) and a 2Gbit(256MB)

And at least we can see that 464MB of RAM are detected by the phone.
[Galaxy S I9000 Android Development] hardcore:
Hey guys, now sure which values the current testing has modified, but these settings should gain us an easy 28MB with no risk.

I compared the Galaxy Tab and Galaxy S configs. In some cases the Tab reserves less RAM, so I just took the Tab's lower value:

SGS:

[ 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

Tab:

<6>[ 0.000000] s5pv210: 4915200 bytes system memory reserved for fimd at 0x40204000 bank 1

<6>[ 0.000000] s5pv210: 37748736 bytes system memory reserved for mfc at 0x3117c000 bank 0

<6>[ 0.000000] s5pv210: 37748736 bytes system memory reserved for mfc at 0x406b4000 bank 1

<6>[ 0.000000] s5pv210: 8388608 bytes system memory reserved for fimc0 at 0x42ab4000 bank 1

<6>[ 0.000000] s5pv210: 1048576 bytes system memory reserved for fimc1 at 0x432b4000 bank 1

<6>[ 0.000000] s5pv210: 8388608 bytes system memory reserved for fimc2 at 0x433b4000 bank 1

<6>[ 0.000000] s5pv210: 4194304 bytes system memory reserved for pmem at 0x3357c000 bank 0

<6>[ 0.000000] s5pv210: 8388608 bytes system memory reserved for pmem_gpu1 at 0x3397c000 bank 0

<6>[ 0.000000] s5pv210: 7372800 bytes system memory reserved for pmem_adsp at 0x3417c000 bank 0

<6>[ 0.000000] s5pv210: 1048576 bytes system memory reserved for jpeg at 0x34884000 bank 0

<6>[ 0.000000] s5pv210: 16777216 bytes system memory reserved for texstream at 0x43bb4000 bank 0

<6>[ 0.000000] s5pv210: 262144 bytes system memory reserved for wifi at 0x34984000 bank 0

Difference:

fimc0 : 14 - 8 = 6

fimc2 : 12 - 8 = 4

pmem : 16 - 4 = 12

pmem_gpu1 : 10 - 8 = 2

jpeg : 5 - 1 = 4

Total = 28M
[Galaxy S I9000 Android Development] dereknas:
How much memory would this yield?
[Galaxy S I9000 Android Development] huxflux2003:
But does the SGS work properly with the tab values?
[Galaxy S I9000 Android Development] knanda:
Can someone post a kernel with 356Mb usable memory???
[Galaxy S I9000 Android Development] INeedYourHelp:
I don't use video calling.

I don't use samsung default music or video app (use rockplayer).

I don't use the samsung default camera app.

With that in mind, what would be the highest amount I can have total? Would it still be 356, or can I scrap some more out of it?

(when I look at the config list, the only things I recognize are jpeg and wifi)
[Galaxy S I9000 Android Development] hardcore:
Just made a kernel with 334MB free. It has:

- Mild compiler optimizations (O3 vs O2)

- Universal Lagfix

- 720P Video Recording works

- 720P MKV Playback works

- "SpeedMod"-ed kernel with jhash3 (will release more info later)

Haven't tested extensively but it *should* work okay. No guarantees.

Memory configs:

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM=4096 *#

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_GPU1=8192 *#

CONFIG_ANDROID_PMEM_MEMSIZE_PMEM_ADSP=1500

CONFIG_WLAN_SAMSUNG_MEMSIZE_BCM=256

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC0=12288 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=12288 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=1024 *#

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=10240

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072

Big thanks to sztupy for his kernel compiler VM.

** FIMC0/2 = Below this and 720P video recording won't work

## MFC0/1 = Below this and 720P video playback won't work (from ykk_fixe)

*# PMEM/PMEM_GPU1/JPEG = Taken from default values for Galaxy Tab
[Galaxy S I9000 Android Development] dupel:
Do share your work =) (want to try out if O3 makes any difference)

Maybe you can add your fix (one that isnt included into universal kernel) the one that remounted /system with noatime. Or even change etx4 mount point so it does less journaling?

Okay, im being sooo demanding :D

EDIT. You did already)))
[Galaxy S I9000 Android Development] INeedYourHelp:
I can flash this right over universal lagfix 0.3, without issues right?
[Galaxy S I9000 Android Development] dupel:
yes

10char
[Galaxy S I9000 Android Development] vanahaim:
Awesome, thanks..

Only question - is possible make UV/OC version?
[Galaxy S I9000 Android Development] jona29:
flashed this with odin phone wont boot now :mad:

anyway to recover this or do i lose everything and have to do a full flash ?

nm sorted it
[Galaxy S I9000 Android Development] dupel:
Possible, but the raspdeep is busy right now. Hopefully he will figure out oc kernel in few weeks =)