yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] vanahaim:
Thanks for reply... :)
[Galaxy S I9000 Android Development] dcarr622:
Any way to get more than 356MB? Currently using the 356MB kernel by sztupy and it seems pretty good. Seeing as I never use video chat, 720p recording, or 720p playback, is there any more RAM that can be freed up or are we stuck at 356MB? It's definitely an improvement but still less than comparable 512MB devices such as the Nexus One.
[Galaxy S I9000 Android Development] INeedYourHelp:
so did you get his kernal to work? Now I'm afraid to try, lol.
[Galaxy S I9000 Android Development] KaliKot:
the kernel worked, and so far so good :)
[Galaxy S I9000 Android Development] d3885u:
What a nice works mate...

But about the speedmod, is it brings a lot of speed improvement when comparing with the "341MB version"?

Waitin for more release info...
[Galaxy S I9000 Android Development] hardcore:
Thanks. I'm also trying out the kernel and it feels fast.

In theory it should be faster. I replaced the Jenkins hash function in the Linux kernel with it's newer version, which is better in every way. Did the same for the Tomato linux router firmware a while back.

After this will try to see if we can get a few more MB of ram without sacrificing any features.
[Galaxy S I9000 Android Development] d3885u:
What an excellent combination when you found a "mix-match" composition between "Quality" and "Quantity" there mate...

Can't wait to see when you find that "perfect-combination" kernel...

Keep all the good works mate...;)
[Galaxy S I9000 Android Development] hardcore:
UPDATE: Just made a kernel with 340MB 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=11264 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=11264 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=1024 *#

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=6144 ^^

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

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

New version with more free RAM. Found that I could reduce FIMC0/2 to gain 2MB while still having 720P video recording.

Also trying out reducing TEXSTREAM - the risk is that 3G video calling might not work (but from previous peoples' comments, it should). Testing and feedback are welcome!

EDIT: Download pulled. Newer version out.
[Galaxy S I9000 Android Development] d3885u:
Hell yeah...this is what I'm looking for...going to flash this kernel right now...

Thanks mate...please keep reporting and updating...:D:D:D
[Galaxy S I9000 Android Development] vanahaim:
Wow, you're a magician.

So far everything works as it should.

THANK YOU!
[Galaxy S I9000 Android Development] zenkinz:
@hardcore,

you deserved a beer (a wizen or tiger)!

I observed that startup is faster now, media scan seems to complete faster but it could well be a psychological eff.

but certainly when I tried the 347mb it wasn't as snappier as the 327mb one, and your 340 one feels as stable as 327mb version if not faster.
[Galaxy S I9000 Android Development] hardcore:
Update: New version to try with additional compiler flags:

-O3 -mfpu=neon -mfloat-abi=hard -ftree-vectorize

This might make the compiler use more of the NEON instruction set in the Hummingbird CPU. Still experimenting, not sure if it has any effect, but using it seems to be okay.

Otherwise it is the same memory config as previous build with 340MB free. It has:

- 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.

EDIT: Download pulled. Newer version out.
[Galaxy S I9000 Android Development] titooo7:
hardcore, is this 340 ram kernel including universal lagfix? thanks for your work
[Galaxy S I9000 Android Development] jplt:
FWIW, I have used the kernel compiled by matthewtse, attached to post #88 of this thread, for 1.5 days now, and everything works perfect! 341 MB, 720p playback and recording work fine, can't test 3G video call because of lack of suitable counterparty. Thanks!

I'd also like to use the opportunity to thank ykk_five for bringing to our attention those memory-freeing opportunities and hardcore and others for trying to push the limits even further!

But sztupy is my hero :D - for ultimately user-friendly set of tools provided to the community, cleverly including all the good bits created previously by other excellent developers, the list of whose is too long for me to memorize and reproduce!
[Galaxy S I9000 Android Development] ykkfive:
thx. hope u'll enjoy it :D
[Galaxy S I9000 Android Development] ykkfive:
while maximing the available mem, i'm working to min the men usage. it can be below 100mb, ie, we can have more then 260mb free mem
[Galaxy S I9000 Android Development] dupel:
Works very well. And fast. But than again your last kernel was fast too (I'd say fastest yet - jhash3 seems to do its purpose). Not sure how much neon does...

btw, are these if you use these neon instructions, do you not use the old (-O3 -march=armv7-a -mtune=cortex-a8), or they can be used together?
[Galaxy S I9000 Android Development] ardf69:
Yes they can. The neon options are used for vectorial operation (for example for cycles with multiplications), gcc unrolls loop and write the code for neon.

Ciao Angelo
[Galaxy S I9000 Android Development] dupel:
Thanks for clarifying.

Tried out the new kernel for a few hours and I would say it is fastest yet. Not very noticably, but Im a speed freak.

First of all with it For the first time I can go over 2k in quadrant, secondly animations are generally a tiny bit smoother and scrolling (for example in browser) is smoother too.

But that again the difference is so small, it could be my imagination playing tricks.
[Galaxy S I9000 Android Development] Ettepetje:
I flashed the 334MB free kernel on my brand new doc 5.1 light (universal lagfix 0.3) setup and it hung at the first boot-screen (30s boot-screen, 20s black, repeat). A full Restore helped. Anyone know what went wrong? (and is there an easier fix)
[Galaxy S I9000 Android Development] d3885u:
Wow:eek:..what a "quicky" progress do make mate...slow down a little bit...:p

Just finished flash my SGS with your newest moded kernel with NEON instruction there...

ehmm...but it seems not so much different with your older mod kernel 340MB version (without NEON instruction)

Thanks mate for the progress that you've made so far..I'm really apreciated for what you've doing here...keep the good work mate...
[Galaxy S I9000 Android Development] Lalaca:
Currently running the NEON kernel on top of NO-RFS ext4. It feels nice, and plays well so far.

Ran Linpack... just out curiosity. It's lower than stock Froyo. O.o;;

A peculiar observation, considering how well it's running. *shrug*
[Galaxy S I9000 Android Development] ashwinds:
hmmm.. i just tried neon and ran QS. The video tests were pretty slow for me ... i could see some jerkiness. I am on jfs - dont know - will flash 340 and check it again if that makes a difference.
[Galaxy S I9000 Android Development] arash64a:
i am using of jpjpa on my galaxy wich kernel u prefer to me for increasing of ram?

thanks
[Galaxy S I9000 Android Development] ardf69:
I don't think you cannot find great improvements since fp and vectorial operations in kernel aren't so much. The kernel so optimized does the difference in IO operations and not in calculus. To find more improvements you need to rebuild the executables (eg dalvikvm).

Ciao Angelo
[Galaxy S I9000 Android Development] ykkfive:
+test2: 258mb free 201010271843HKT

pls see post 1
[Galaxy S I9000 Android Development] EarlZ:
Can this kernel work with Doc's v5.1 ?
[Galaxy S I9000 Android Development] SetiroN:
Could you elaborate on what changes you made? :)

And by the way, what would happen if you completely removed those parameters? Any chance those hardware fuctions could start using allocating RAM dynamically?
[Galaxy S I9000 Android Development] dupel:
Without some phone wont boot. I guess only cyagen could fix this.
[Galaxy S I9000 Android Development] sztupy:
One might try switching from discontigmem to continous memory, but for that we have to recompile all modules. Unfortunately some kernel modules have no corresponding source code present, which would make this change even harder. Some kernel modules aren't really needed (like rfs :) ), but some others are (iirc the display module and the onenand fsr driver. I might be wrong though)
[Galaxy S I9000 Android Development] mapas:
it depends how good the modules are programmed. if they do proper checks about the type and size of memory then they might work...

if they developed them using hardcoded stuff (which is probably the case) then we need to edit their source code too, and i am not sure it is worth it...
[Galaxy S I9000 Android Development] sztupy:
most of the modules are taken from the linux kernel, so they should work. The closed source variants won't work of course, as they are compiled for a different memory model (running them will result in either the module not loading or a "simple" kernel panic). The ones that are open, but not from the base kernel tree might be problematic (but still not as problematic as the closed source ones)
[Galaxy S I9000 Android Development] halabibk:
I think cancel all parameter some app should work and some not, but we can use 3rd party app that no need to reserve memory and at least we can see 448. Can any one make the kernel without memory reserve and I will try it.

Thanks.
[Galaxy S I9000 Android Development] hardcore:
Next thing I am trying: Change the kernel HZ value from 250 to 100. In theory this should improve battery life, but not sure if the decrease in timer resolution is noticeable to the user.
[Galaxy S I9000 Android Development] huxflux2003:
I think that the I9000 is tickless, so changing CONFIG_HZ will not do anything. You could experiment with preemption though, which is set to "n".
[Galaxy S I9000 Android Development] knanda:
Can anyone post the 356MB kernel please??
[Galaxy S I9000 Android Development] arash64a:
can we flash your kernel on any fw like jpa or any other?
[Galaxy S I9000 Android Development] sztupy:
Yes, tickless kernel is enabled in the default config file
[Galaxy S I9000 Android Development] bilboa1:
you guys tried video out ? ;)
[Galaxy S I9000 Android Development] hardcore:
UPDATE: This post is outdated. Please go here for latest updates on this kernel.

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

UPDATE: Updated kernel with 340MB free. It has:

- Based on JPM kernel

- Includes sztupy's Universal Lagfix

- Reduced HZ to 100 for (hopefully) better battery life

- 720P Video Recording works

- 720P MKV Playback works

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

- Compiler flags (ver A): -O3, -mcpu=cortex-a8, -mthumb (download removed)

- Compiler flags (ver B): -O2, -mcpu=cortex-a8, -mfpu=neon, -mfloat-abi=softfp

- Compiler flags (ver C): -O2, -mcpu=cortex-a8, -mfpu=neon, -mfloat-abi=hard

- Compiler flags (ver D): -Os, -mcpu=cortex-a8, -mfpu=neon, -mfloat-abi=hard (experimental)

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=11264 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC1=1024

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMC2=11264 **

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC0=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_MFC1=30720 ##

CONFIG_VIDEO_SAMSUNG_MEMSIZE_JPEG=1024 *#

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=6144 ^^

CONFIG_VIDEO_SAMSUNG_MEMSIZE_FIMD=3072

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

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

*# PMEM/PMEM_GPU1/JPEG = Taken from default values for Galaxy Tab

Big thanks to sztupy for his kernel compiler VM and ULF, lastufo for working on compiler optimizations, ykk_five for testing memory configs, and others who gave ideas or helped.

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

EDIT: Uploaded 2 versions with different compiler settings for testing.

Ver A is more experimental. (removed)

Ver B is using O2 (341MB free) and softfp support.

Ver C is similar to B but might be faster (hardware fp only).

Ver D is similar to C but optimized for size. (342MB free!)

Suggest to try Ver D.
[Galaxy S I9000 Android Development] hardcore:
Thanks for the input guys, but I think HZ is still used. Tickless mode is an enhancement.

There is definitely some difference - I notice that the cfq scheduler slice options have changed their timings a bit (now they are multiples of 10ms, previously with HZ=250 they were multiples or 3 or 4ms). But otherwise everything still works okay. Will use it for a while to see if it improves battery life - some Linux notebook owners report good battery life gains by switching to HZ=100.
[Galaxy S I9000 Android Development] ykkfive:
lower mem usage updated 201010280000HKT (pls refer to post #1)
[Galaxy S I9000 Android Development] EarlZ:
@hardcore

Is this the same Kernel thats with Doc's v5.1, aside from the 340MB usable ram or its just a stock kernel with 340MB ram ?
[Galaxy S I9000 Android Development] EarlZ:
Looking at the diagram, theres 1Gb DDR dedicated for the baseband processor, 8/16GB MLC NAND and 2Gb DDR to the application processor.. Im wondering why theres a need for samsung to reserve a space on the 512MB ram thats usable for us..

Im totally ignorant on why theres a 1Gb RAM on the baseband and 2Gb RAM on the application processor.. I mean, I thought everything works around the 512MB RAM.. anyone care to explain in detail??
[Galaxy S I9000 Android Development] vanahaim:
Works fine, I'm curious about battery life.
[Galaxy S I9000 Android Development] dupel:
The same, based on universal source.
[Galaxy S I9000 Android Development] hardcore:
It's based on the JPM kernel with Universal Lagfix.
[Galaxy S I9000 Android Development] EarlZ:
Good, It also has the BLN right ?

EDIT:

NVM, found the answer.. Universal lagfix already has BLN enabled.
[Galaxy S I9000 Android Development] zenkinz:
did you try the memory config ykk_five used to yield 356mb ram?
[Galaxy S I9000 Android Development] hardcore:
Not yet. Those will break certain features like 720P recording and playback. I'm trying to find a minimum where everything still works.
[Galaxy S I9000 Android Development] avary:
care to share this killer script ?
[Galaxy S I9000 Android Development] EarlZ:
Making a nandriod backup and will give this a try with Doc's v5.1.. hopefully all goes smoothly.

Disabled the BLN and start up tweaks just incase it may mess it up.
[Galaxy S I9000 Android Development] dupel:
No need for both. Kernel doesn't influence data, and tweaks are applied post boot as scripts.

And if something does go wrong you can just flash normal universal lagfix kernel which will fix everything.
[Galaxy S I9000 Android Development] EarlZ:
I can tell that the effect of having more free ram on the SGS is definitly a HUGE plus, I no longer get the micro-stuttering after opening several apps!

Should we still continue to use autotask killer?
[Galaxy S I9000 Android Development] zenkinz:
cool.

anyway, it looks like you have drop neon instruction set support in your latest research, true?

edit: my bad, just saw you uploaded a neon version of your latest research.
[Galaxy S I9000 Android Development] hardcore:
You shouldn't use the ATK app. Autokiller (minfree settings) is okay, but its not really needed since Samsung already configured Android to keep free 48M of RAM or so.
[Droid Incredible Q&A, Help & Troubleshooting] ryandroidryan:
Is there a known kernel that will run with jager 3.2, faster then 1.19ghz(kingxkernel 5)?, or is there a better rom that is working with all features and fast, i have not been able to get cyanogen 6.0.2 to load for some reason, and I like the jager rom, vanilla is pretty good but my camera would not save pictures?
[Droid Incredible Q&A, Help & Troubleshooting] hockeyplayr:
im using skyraider vanilla 3.0 RC3 rom with the same king kernal. Its been smooth and fast, and i have encountered no problems so far.
[General Questions and Answers] Zweihander:
Hi, I recently replaced the screen on my Samsung Vibrant because the previous screen had broken. Unfortunately, I had mistakenly taken the sensors for the 4 main function buttons with my efforts. As such, I was wondering if anybody knew of an app that would replace these 4 function buttons through a software solution? Possibly an app that places them in the pull down menu as an ongoing program?
[General Questions and Answers] stragulus:
Interested in this as well. Although I do still have working volume keys, those could be mapped to one of the other functions. But I'll start a new thread on that elsewhere.
[General Questions and Answers] Zweihander:
If there isn't an app, can anybody think of a workaround?
[XPERIA X2 General] Lerka:
So my X2 died completely about 2 months ago. I went to the store where I got it to find out that they have no refund/return policy. The guy promised to send it back to Hong Kong,,, but I doubt that he ever even sent it (no paperwork..nothing):confused:. And then he says it's LCD issue and I have to pay $150 ... sounds fishy, doesn't it? Anyway, I went to Flextronics in Newmarket and they can't do anything because it's not a Canadian model and it's never been released here!!! :mad: kill me now!!!

So what the heck do I do now? Any help/suggestions? Can I send it anywhere?

Or just forget it, curse SE and recycle this piece of ****?
[XPERIA X2 General] mrqro:
well basically SE X2 is a luxury phone and it should have internationall warranty

if you baought this phone with papers from that shop you should really sue that guy

if not maybe if you better describe the fault we can help you

have you tried calling SE Support line to get some knoledge about where u could reapair it near you?
[XPERIA X2 General] Lerka:
There is nothing to describe really. I did hard reset bc you know X2 is a living hell and in the middle of it, it just turned off. The light doesn't flash when charging, doesn't turn on...it's just dead

I contacted the SE Canada. They said I have to send it to US bc X2 is a Grey Market phone and cannot be fixed in Canada. And the service costs $185 + I have to give them US address to ship it back

So much for the luxury phone with international warranty. FML! Never ever buying SE again!!!!!! :mad::mad::mad:
[XPERIA X2 General] Basharca:
Dude this happened to me as well, and se replaced it for me for free. Yes they gave me a new phone, which was another x2.

You should contact se themselves and explain for them the problem. They will ask you for the invoice and IDME number, after that you just need to wait for a while, maybe 2- 3 weeks and they should ship you your new phone.

The very cool thing about xperia phones is that they have an international warranty so you should take the advantage of such thing.
[XPERIA X2 General] Lerka:
I called SE Canada and they said I have to ship to US service centre but if they can't fix it they won't give me new phone, I asked.

Where did you call?
[Vibrant Android Development] boimarc89:
This is an proactive effort to get an .apk for a Gallery3D.apk lockscreen. from past experiences, i may have to try coding this myself from lack of response , if anyone wants to help me, lemme kno.
[Vibrant Android Development] creator2456:
Not sure what exactly you are looking to achieve:

A security lock for opening the gallery app?

or

The gallery showing on the lock screen?
[Vibrant Android Development] ags29:
There's many apps on the market that allow you to lock your gallery very effectively, I don't know what extra security this would achieve?
[Vibrant Android Development] b0ricuaguerrero:
photo vault does the job
[Galaxy S I9000 Android Development] dahuzi:
I struggled two days with the blooming versions of JP6/JPM kernal without success. So I have to think I am the only unlucky guy in this forum.

Before the voodoo froyo support come out, I was using JPM with CF-lagfix 1.9, no any problem. After voodoo 5 pre 4 released, I tried to apply it. Then the painful struggling started.

Here are the approaches I did:

Approach A: Uninstall the CF-Lagfix through PC tool, then flashed the voodoo 5 pre 4 kernal through Odin. After reboot, stuck at S logo with vibration a few times, then screen went to blank but still periodical vibration. Reboot again and did factory reset. Same.

Approach B: Flash back stock JP6, rooted with CF-Root, then repeat approach A but repeat the problem.

Approach C:

Step 1: Flash a stock 2.1 ROM ZSJH1(Hong Kong version)

Step 2: Flash a Froyo stock version DXJP1 for Asia (if I flash JP6 directly onto a 2.1 ROM, I got the error message : Can't mount /dev/block/st110)

Step 3: Flash the stock JP6.

Step 4: Rooted with CF-Root.

Step 5: Flash the "universal lagfix kernal alpha 1" kernal, in lagfix option, I choose voodoo, then the recovery show clearly steps of backup/unmount/creat/restore... without any error message. After that, phone rebooted automatically. Still stuck.

Step 6: Did factory reset, no help.

Step 7: Reboot into recovery, disable the lagfix and reboot, same problem.

Approach D:

Repeat Steps 2-4 as C, apply the Doc'Mod barebone version zip file in SD card through CWM, after rebooted, goto recovery and apply voodoo lagfix. Result same. Did factory reset before and after, didn't work.

Approach E:

Repeat steps 2-4 as C, apply Darky's Raw Steel Edition 2.2 from SD card. The phone booted, but it's very laggy, even worse than the stock JP6 without lagfix. Then I put "disable-lagfix" folder inside the voodoo folder in SD card, reboot, system refused boot-up but stuck again.

Now I have to go back to the newest Hong Kong version ZSJP8 with OCLF. System runs very smooth.

Anyhow, since I feel I am quite familiar with Android system flashing (I used Milestone a few months, flashed the different ROM more than 50 times, and N1 one month also flashed many times the customized ROM. Even for SGS, also more than 20 times to try the new versions), this is the first time I face so weired problem. I still would like to give a try for the new kernals, but I really need to know the reasons behind. I searched the forum, seems I am the only guy to have such difficulties.

Sorry for my English as I am a Chinese, but any comments are very appreciated.
[Galaxy S I9000 Android Development] RyanZA:
Flashing custom kernels can be hit and miss for certain devices - possibly because of hardware differences between regions or something strange. You're not the only one. ;)

An option you can try though is to patch your own region's stock kernel with z4mod. No guarantees, but it's something you can try. :)

Online patcher available here: http://www.sgscompilebox.dreamhosters.com/

(Still alpha)
[Galaxy S I9000 Android Development] wangbin:
jp8+voodoo的方法是你刷完jp8.，后直接刷voodoo-5-pre6，然後再root，利用電子市場下載mount system，然後開啟system的可讀可寫。jp8+super_kernel的方法跟上面一樣，能不能root還在試驗中。原諒我的英文比你還差
[Galaxy S I9000 Android Development] dahuzi:
Thank you first for your great work for those easy tools for root, lagfix.

My phone was bought in Hong Kong, and many mates surround me (in China) are same, but everybody then claim the succeed to apply voodoo onto JPM/JP6. So far the only working lagfix method for my phone is OCLF.

Regarding the different method, what's your opinion regarding the Ext2 and Ext4, are they really behave so noticeable difference? Your opinion will determine my next try:D