yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 General] ivan1975:
Hi, on android 2.1 these lags are not so evident. I upgraded my phone to android froyo 2.2 and I had some lag issues. But after disabling the default keyboard things seem better. I have a score of 1008 on quadrant benchmark.

In my opinion if you don't see the need of a fix you don't have to apply any fix. I think that applying these fixes you could void the warranty of the phone. So it is why I am waiting to do this. I am reading around other post and there are different opinions about the better and safe filesystem to use.

To answer a previous question, ubuntu uses as default the ext4 filesystem: https://help.ubuntu.com/10.10/hardware/C/disks.html

and not the reiserfs.

But I am still curious to see if there is any difference between reiserfs 4 and ext4 on this phone. Just curiosity.

Ciao

Ivan
[Galaxy S I9000 General] richie.aks:
Thanks for the quick reply ivan. In conclusion, i should stick with what i have if i want to have a stable and fully functional Samsung Galaxy S GT-i9000. Right?

And wait for a stable or final version of Froyo 2.2. Right?

Note: Can i be "directed somewhere" to read on the difference of Eclair, Froyo and other roms?
[Galaxy S I9000 General] ivan1975:
Hi, I think that the best thing is to read all the posts and to make your personal opinion on this. As you I am new, and I am only trying to understand. But for sure don't make nothing before to know exactly what are you doing. Bests

Ivan
[Galaxy S I9000 General] Seifer1975:
I dun understand why stock froyo is so much more laggy than eclair? I tot that froyo is supposed to bring speed improvements?
[Galaxy S I9000 General] WarriorZ:
I think the lag problem is because the factory reset / data wipe not execute before and after upgrade firmware.. CMIIW
[Galaxy S I9000 General] ivan1975:
I didn't make the factory reset!!! Can you explain why things are better enabling the swype keyboard?

Maybe I must make the factory reset..
[Galaxy S I9000 General] ivan1975:
I made the factory reset and the behavior is exactly the same. The same score in quadrant.
[Galaxy S I9000 General] ivan1975:
I would condivide an answer I received from the SAMSUNG customer care about the lag fixes:

So in theory the lag fixes could void the warranty of the phone. But, they said that if and only if the lag fixes were not initially developed by Android and are not compatible the warranty will be erased. Well this for me means different things:

- ext4 filesystem is part of linux and so of android

- the voodoo kernel starts from the source released by samsung, a gpl code that can be modified by users...

- not compatible/compatible this could be the key of the question, because I read in different posts that it is unknown how the samsung filesystem is working, someones argue that it is doing something more than the journaling. Maybe, the use of the ext4 filesystem could be different from the samsung one resulting in an unpredictable behaviour of the hardware. In my opinion this point could be use by samsung to reject the request for warranty in the presence of a modified galaxy s phone.

I found also interesting that they currently don't know if an official fix will be included in a revision of Froyo.

I would also ask to supercurio if he had taken in account the possibility to contact Samsung to condivide his fix with them. This maybe could facilitate the release of an official fix.

Ciao

Ivan
[Galaxy S I9000 General] er_arbe:
noob

Hi,today I have purchased a samsung galaxy s from Orange.It is supposed to arrive in 5-7 days. I have been reading some post and now I know the lag issue. I have some questions:

a) do all SGS have this issue???or just some of them???

b)Which fix method is more secure to revert??I mean,if whatever happens to my phone,and i have to send it to the technical service,which method is easier to revert,so they can´t tell me anything about warranty.

Sorry for my poor english,and thanks a lot in advance!!!!!
[Galaxy S I9000 General] fane1:
Samsung will never fix the lag in sgs my friends.You know why?

For example if i give a galaxys to my mother she will never complain about the lag because she is a normal person who is used to a nokia n95 and so she would never notice that.Its some of us,especially the speed freaks that are complaining and i must say with the right reason but again,we are few amongst 5 million units sold so far.

What samsung will do and thats their behaviour from the last years is to move on and buit a new device,fixing the bugs reported by "US" with the former model.Galaxy tab doesnt lag and its the same hardware that our phone has ans i bet that the suposed galaxy 2 will be a much better phone.

Speaking about my experience with lagfixes and custom kernels ive tried so many things since the beggining that actually im not using any lagfix at all.Just an optimized kernel will handle your phone if u dont install too many aplications like i do.
[Galaxy S I9000 General] Chad_Petree:
what im curious to know is why if the galaxy tab uses rfs it doesnt lag :confused:
[Galaxy S I9000 General] zoubidou:
difference pad to phone

first of all, i don't think you use a pad like a phone, thus there are probably lags in the pad which you don't see because of the different usage.

second the pad is bigger, if it would have the same components, it would have the same lags, but there are possibly different components in there like faster memory, which where whether not available when the phone came out, or they just where to big to fit in a phone. you don't have the same cooling problems either, and so on.

I upgraded to FROYO through KIES and gained about 200 in quadrant bench. it went from something around between 850 to 1100, without changing anything on the phone. thus froyo increases speed somewhat.

For instance I am using the YA-OK kernel which includes also some OC. and the boot speed is devided by 4. when i reboot it comes nearly immediately to the bootsound and screen and this does not last long not either, while the stock version takes nearly a minute for evertyhing, without counting the eternal file system scanning, which is really a hazzle.

The RFS file system comes from REXX File System.

It does not mean Remote File System!!!

you can find any information about it there:

www.samsung.com/global/business/sem...memory/downloads/rfs_v12_application_note.pdf

it is based on FAT32 and modified to not to interfer with any MS copyrights.

FAT32 exists since the late 80's and is still very much used in external harddisks and other portable memory devices (including but not exclusively USB). it has also the advantage of being easily used as a ram drive and things like that.

It has known advantages (simplicity) but also a lot of disadvantages, especially concerning franctioning and indexing, which makes this filesystem rather slow.

So if you you have the feeling that your phone does not respond as it should, then you find answers here of how to make it faster. But if you don't think this is the case, why bother, just keep it stock as it is.

Besides that I figured out that it is really hard to brick a galaxy s. In fact it is nearly impossible. Sometimes you just have to remove the battery and possibly the SIM and let it sit there for 15 minutes or more, but afterward you can again start it in download mode.

The only thing you never touch is the initial boot loader.

well thats all for know.
[Galaxy S I9000 General] ivan1975:
I applied the voodoo lagfix from supercurio. The phone now is really usable as pda. Big improvement. But for beginners I will wait the update.zip package. Very nice job!
[Galaxy S I9000 General] ippocampos:
SGS I9000 gingerbread.xxjvt

i have gingerbread.xxjvt firmware 2.3.5 OCLF AND Z4 MOD doesnt work for me can anyone help me whitch is the proper voodoo edision to download??? thanks
[Galaxy S I9000 General] Furry Atom:
Why the hell did you bump a thread from over a year ago? What is with new members and bumping insanely old threads? They should be handing out permabans for that kind of crap.
[Galaxy S I9000 General] evildude88:
Hi there, sorry to keep an old topic but I felt it was better to use this than to create a new one.

My question is about doing these lag fixes to the ice port. I am wondering if it works or not? I would like to improve the read/write speeds if I can..

Thanks!
[Galaxy S I9000 General] fylim:
My best suggestion to anyone with general lag issues to

1. Get on Simplicity ROM 2.1 (jvz)and of to 1200mhz

2. Convert to Ext4 for all partitions including system.

3. Disable apps you don't need to auto restart using Autostart app.

4. Remove apps you don't need as some introduce add hooks/bavkgound services.

Your phone's performance in terms of responsiveness will mostly be faster than most phones even some stock S2.

And quadrant can reach 3500+ if it means anything to you.
[Galaxy S I9000 General] Evans_Prophet:
RAID - Who is going to implement it first?

As said on another post, Linux seems to support RAID quite easily. I don't know about potential CPU strain - remains to be seen.

The experts here will have a much better view, but I think compiling a kernel with RAID support (if not already in there) should not be very difficult.

Of course Android is a different beast, but the developer who would achieve this would certainly gain the honor of being the first one (?) in history to implement RAID on a mobile phone... :-)

----

SEE

https://raid.wiki.kernel.org/index.php/RAID_setup

https://raid.wiki.kernel.org/index.php/Linux_Raid

(some info on the matter)
[Galaxy S I9000 General] kenkiller:
That would be purely for bragging rights, not necessary useful on a phone. Pointless. :(

I'll settle for something that works great, and safe.
[Galaxy S I9000 General] xtrememorph:
Rooted SGS Stock with Autokiller seems to make the phone really snappy without One Click Lag Fix.
[Galaxy S I9000 General] dupel:
No it does not. Its just hands growing from wrong parts of anatomy.
[Galaxy S I9000 General] hardcore:
I agree, and I think the real lag fix is the tuning of Android's built-in lowmemorykiller to be more aggressive.

The file system lag fixes are more of "performance boosters" because although they do make the phone faster, they don't really fix the low memory lags.

Still, can't wait for the Voodoo lagfix to get ported to Froyo. That would be awesome.
[Galaxy S I9000 General] Adevem:
i've personally only tried RyanZA's one-click lagfix 2-3. was pretty awesome.

i went to jm1(rev 3) and things are pretty smooth now without a lagfix. except for some lag when putting icons on the homescreen, all's not too bad.

manually removed bloatware by samsung and it's looking quite alright.

of course, i want my voodoo and froyo now! :cool:
[Galaxy S I9000 General] robnil:
I have tun autokiller and ryanZA (the one on the market) and sure i get 2200 score and it felt really snappy the first 2 days. But now it is worth than ever.

I have missed a couple of calls due to the freezelag.

Sure I have installed a couple of apps after the fix was installed, but most of them are uninstalled again in a desperate try to get the phone to be usable again.

When I tried out the phone out-of-box it was in no need for a lagfix. Then things got worse...

The version of ryanZA one-click that i used is 1.6.5.
[Galaxy S I9000 General] xtrememorph:
Did you preset the autokiller to strict? If not give it a try.
[Galaxy S I9000 General] rui.mamede:
How can i access that "lowmemorykiller"?
[Galaxy S I9000 General] distortedloop:
Get AutoKiller or MinFreeManager from the Market.

Don't let AutoKiller (my recommendation) name fool you, it is not a task killer, and you don't want to use any old task killer like ATM or the like for this.

Install Autokiller, check the presets, select strict or aggressive, hit apply. Also in the settings select apply at boot.

Edit: if you're a roll your own kind of guy you can also just echo the 6 settings to the proper location via terminal or script.
[Galaxy S I9000 General] rui.mamede:
I know about autokiller from market, just wondered what he meant by "built-in"
[Galaxy S I9000 General] xtrememorph:
I believe he mean edit the config file directly in the system.
[Galaxy S I9000 General] distortedloop:
By "built-in" he meant Android's low memory manager, the thing that AutoKiller adjusts.

Hardcore started a thread where we discussed this in more detail here, where it's clear from the context what he means. ;)
[Galaxy S I9000 General] hardcore:
Hi rui, by "built-in" I was referring to Android's own task killer. Android has an intelligent automatic task killer, the "lowmemorykiller" module. Normally the parameters of this module are not configurable by the end user.

Apps like "Autokiller" or "Minfreemanager" let the user change the configuration of Android's lowmemorykiller module. These apps don't actually auto kill any processes - they just configure Android's lowmemorykiller module to tell it how low the free memory can go to before it should kill processes.

You need to have root for it to work.
[Galaxy S I9000 General] rui.mamede:
Thanks hardcore, distortedloop and xtrememorph for your replies, I'm elucidated :)
[Galaxy S I9000 General] richardbroder:
I use RyanZA's lagfix. I do have one question about it. When you apply the lagfix it asks you for the file size (that will rest as application data) that should be created. The stock option is set at +1.6GB eating nearly all the app memory available. Although I have few apps installed (less than 20mb) I set the file size of the lag fix at 1GB, I do this because the quadrant benchmark will give the exact same results independent if I use a 1GB or the stock 1.6GB file size, so I select 1GB just in case I will need that extra 1GB for apps. What is, after all, the right file size for apps?
[Galaxy S I9000 General] distortedloop:
Only you can decide what is the right size, but you're a little confused as to what's going on it seems. The 1.6gb default size is where your apps will go once the fix is installed. So, by making that size smaller, you're actually reducing the amount of space available for installing apps!

This is one of the problems with OCLF in my opinion. It's two-fold. First, the apps free space is not accurate, and second that huge 1.6gb file really screws up nandroid backups in terms of size and storage space for them.
[Galaxy S I9000 General] een625:
Just a thought...

If you want to check your "real" apps free space, download oneclick lag fix on the market, and click on check free space...
[Galaxy S I9000 General] richardbroder:
Hmm, so what´s the advantage of choosing LESS app size?

Btw, I don´t really care about the task manager showing less app memory than there actually is, as long as it´s there... I only use about 20mb in apps anyway, just want to know what´s the advantage/disadvantage of choosing more/less file size in OCLF
[Galaxy S I9000 General] distortedloop:
Primary advantage - if you use Clockwork to make nandroid backups, they will run faster and take up less space on your sdcard. The entire space you allocate to apps is written as a file to the internal storage, regardless of how much space your actual apps use, so even if you have zero apps installed, a nandroid will use up 1.6 gb of storage space to back up that file.

I don't really care about that either, but there are enough complaints about it scattered around that it's clear some people do. It's just important that you know this before you start, because the first complaints people who didn't read all the posts on the OCLF make is "how come I only show xxx amount of space for apps after installing this?"

I think there were also complaints of people not being able to install certain apps because of the low space reported. You'd have to search the various OCLF threads to clarify that, though
[Galaxy S I9000 General] danamoult:
Why exactly is it said that Voodoo is the 'best' one coming out?

And does it require you to flash a new kernel? In my mind that raises the difficulty of installing it over some of the other lagfixes.
[Galaxy S I9000 General] distortedloop:
Because Voodoo does what we've all said Samsung should have done in the first place - it replaces the default RFS filesystem with ext4. Both are journaled, but ext4 is so much faster. If Samsung would just do this in the first place, we wouldn't need lag fixes. Once it's in place, it's simple, over and done with.

The mimocan approach sort of takes that approach, but it doesn't replace the RFS, it just ignores it for part of your /data partition by moving stuff onto an ext4 filesystem, but requires an external sdcard and creating symlinks. Once it's in place, it's simple, and over and done with.

The loop mount methods create a large ext 2 file, then loop mounts it and makes mount points to this ext2 on top of RFS file. It doesn't require a special kernel, but does all kinds of stuff at boot time. Once it's in place, it still has to do all its stuff for mounting at boot time, I honestly don't know if that's simple or not.

The loop mounts seem the most complicated to me.

Voodoo 2 will be done via update.zip instead of via Odin, ultimately, supposedly.
[Galaxy S I9000 General] RyanZA:
The loop mount method is by far the most simple. The mounting it does at boot time is 2 lines of script, and takes well under a second to run. The loop mount method is also much safer than changing the kernel for novice users imo, since the SGS itself will actually remove everything if something goes wrong (the user would lose their data though)... and you're not messing with the kernel. ;)

In Froyo, when you use the apps2sd feature, it actually uses loopback mounts which work in almost an identical way to the lagfix at boot time. So it is a long way from complex. ;)

You can flash the kernel with redbend though, in an update.zip or inside an app, which lowers the difficulty a lot. An app version can also make sure to fetch the correct kernel for your device in a download. I got the go ahead from supercurio to make an app version to do some checks and download the kernel for you. I'll release that when supercurio releases a public version, so it'll hopefully make it easier. :)

The voodoo method fully gets rid of RFS though, so it speeds up both large operations and small operations. This means it helps a lot for installing apps compared to the loopback versions, but doesn't actually affect speed inside most applications themselves. It is slower for small file operations than the loopback version, since it uses journaling (visible in quadrant scores, and yes, quadrant isn't 'wrong' somehow.)
[Galaxy S I9000 General] rui.mamede:
So i guess we have to choose, either belive in you, or in Cyanogen?

http://briefmobile.com/cyanogen-demonstrates-quadrants-flaws
[Galaxy S I9000 General] RyanZA:
Correct. :)

Just kidding. You need to read and understand what Cyanogen is saying. Understanding is difficult, I guess. Unfortunately, the person writing that article didn't understand either.

Cyanogen advised Android users: “Don’t rely on this stuff as your guide to how fast your phone is. There are a lot of other factors.”

Just because I/O is better, doesn't mean that your phone will be faster at anything that doesn't involve I/O.

There are no actual flaws in Quadrant that can be fixed.
[Galaxy S I9000 General] andrewluecke:
Actually, that discussion is about tmpfs.. Benchmarks are ok, but how many people have actually reviewed the code for Quadrant? Technically, it might only test usecases which might be faster, others might be slower.

So Benchmarks are only a tool, and aren't as useful as profiling + real world apps.

However, to say there are no flaws with Quadrant, is complete crap. All benchmarks have flaws. And stuff such as benchmarks are likely to get bigger boosts by JIT. So don't believe that a 3000 score on I/O instead of 1000 means it's 3x faster.
[Galaxy S I9000 General] RyanZA:
I also believed Quadrant was wrong and incorrect until I tried it myself.

I did my own tests using databases reads/writes and file read/writes. Exact same results as given by Quadrant. It really is that much faster. Quadrant (and my tests) just make a few random reads and writes into a normal Android sqlite database. The scores given by Quadrant reflect this completely. They are not wrong, and therefore can't be fixed.

So yes, a higher score on I/O in quadrant really does mean I/O is really that much faster. (not all I/O, just the I/O tested by Quadrant) Test it yourself.

There is a valid argument here: Quadrant gives too much weighting to database reads and writes compared to other benchmarks. Whether or not this is the perfect weighting is completely up to debate, or if even a perfect weighting exists at all.
[Galaxy S I9000 General] kenkiller:
Anyone interested in seeing the over-importance that Quadrant places on I/O should get a copy of Quadrant Advanced.....it only shows how little importance one should place on the final Quadrant score.

It might be useful for bragging rights, but it's not an accurate gauge of performance in real life.
[Galaxy S I9000 General] distortedloop:
Hey, something we actually agree on. ;)

i/o makes a world of difference on any device, and should probably be weighted more heavily than not. Real world proof of that for me is that upgrading one of my 3 year old MacBook Pros from a platter based harddisk to an SSD breathed a whole new life into the machine; it was enough to keep from upgrading the whole laptop for another year (with SSD).

The performance was so much better that I upgraded the boot drive in my Mac Pro desktop to an SSD as well. The laptops and Desktop turn on almost instantly, apps open almost instantly, etc, etc. i/o is a big factor.

That said, there is something wrong with the weighting of i/o in Quadrant, since my phone with a Quadrant score of 2200 on OCLF did not feel any faster than my phone on Voodoo Beta1 with 1750 Quadrant, and the Voodoo fix never freezes or lags, where as OCLF does (for me) on occasion. With that in mind, there has to be some better way to compare these, the i/o may be faster on Quadrant with OCLF, but that doesn't make it the "best" lagfix, in my opinion.
[Galaxy S I9000 General] hardcore:
A question to the lagfix devs: Would it be possible to build a lagfix that is similar to Voodoo, but reformats the internal /data partition using ext2 instead of ext4 so that it doesn't require flashing a modified kernel?

I ask because if that's possible, then it should also work for Froyo builds.
[Galaxy S I9000 General] kenkiller:
Er....it's not the filesystem that's preventing it from working on Froyo.
[Galaxy S I9000 General] RyanZA:
This is actually possible using 2 methods)

1) Replace the ramdisk part of JPC stock kernel, and replace it with one that can do the lagfix.

2) Repartition /sdcard (6gb) into /sdcard (4gb) and /sdcard2 (2gb).

Since the MBR is overwritten by the stock kernel at boot, this repartition will have to be done on each boot inside playlogos1. However, /sdcard is not touched during the boot up procedure, and FAT32 stores all of it's meta data at the front of the partition.

The problem with doing this in playlogos1 is that the kernel will not re-read the MBR until either a reboot (won't work), or until a tool like 'partprobe' or possibly 'sfdisk' is used. The problem is that nobody has yet compiled gnu parted for the stock samsung android kernel.

Once somebody manages to cross compile gnu parted, the rest should be simple.
[Galaxy S I9000 General] hardcore:
Thanks for the explanation, RyanZA. It's appreciated.
[Galaxy S I9000 General] monyozt:
will i loose my fix lag if i restore default my sgs?
[Galaxy S I9000 General] MZWiZard:
+1 for Voodoo lagfix with EXT2 :cool:

Wouldnt it then be possible to make a script, that gets called as the very last thing before phone powers down - and if it didnt get called, it would automatically check filesystem on next boot?