yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] efegue:
It already is ;)
[Galaxy S I9000 Android Development] kenkiller:
Heheh...let's not make him too comfortable with success. :D Familiarity breeds contempt. :D

There's always room for improvements...looking forward to each update. :D
[Galaxy S I9000 Android Development] Arkanius:
To be honest, I don't like the lagfixes because I've already suffered huge databases corruptions using ext4

However, JFS (Still haven't applied since I'm on JPK) feels like the best solution in terms of speed-safety since it's journaled

People saying the speed is very good (although slower) than ext4 confirms my expectations.

I'm in love with this community work
[Galaxy S I9000 Android Development] bilboa1:
i dont think any fs is safe, but ext4 changed from writeback to ordered default to avoid any possible loss (hey it might still happen)

the thing is, most other journaled fs work in a similar way as writeback ;)

that said, running JFS atm as i said it seems to work well.

on a side note, even if its all called "lagfix" i think its more than that and it's not really about being "the king".

This kernel + ramdisk implements most solutions we have found here and in a clean way which just seems to work. That is cool. Devs can keep working on their projects and this one just put them together, some cooperative work, i like it.

For example i'm eagerly waiting for curio's advances on screen color and sound, it would be nice to have them integrated here when it's ready, etc. Beauty of open source :p

just don't forget when you feel like donating, to donate to the guys you feel deserve it not just the one who release the most polished thing (although he's not to be forgotten either)
[Galaxy S I9000 Android Development] musznik:
but what about /system ? still RFS :/ wiating for mod.
[Galaxy S I9000 Android Development] _JKay_:
Running 0.1 overkill option with bind:

Market apk just gave me a FC! I think it was because I updated two apps at the same time without waiting for each to finish first.

Feature I would like in the recovery options:

* Fully Deodex and Fully Zipaligned all apps

* Move Samsung apps to /data/app (Aldiko Books, Buddies Now, Days, Dualclock, Infoalarm, Layar, Memo, Mini Diary, Talk, Write and Go)

* Replace TWLauncher with LauncherPro (completly remove TouchWiz and all its widgets)

* Set Wifi-Off time when screen Off (like in OCLF 2)

* Set Autokiller parameters (like in OCLF 2 and Autokiller)

* Option to include TaintDroid in Kernel

* Boot and shutdown sounds ON/OFF

Has anyone benchmarked the loading of APKs: Deodex vs Odex

Its CPU speed vs filesystem read speed right!

Is odex alot faster to load? Can you actually have .odex files in the /data/app folder?
[Galaxy S I9000 Android Development] sztupy:
Android can usually only load odexed (optimized) files. If it finds a deodexed (unoptimized) file it first odexes it back in /data/dalvik-cache, and runs it from that location.
[Galaxy S I9000 Android Development] xtrememorph:
sztupy, i would like to see the universal lag fix CWM able to install ROM and load backups that is prior to universtal lag fix CWM.

i was able to restore my backup or reinstall rom using the universal lag fix CWM, however than i would lost universal lag fix recovery and phone wouldn't start stuch at Samsung logo screen.
[Galaxy S I9000 Android Development] INeedYourHelp:
I like the ones in bold.
[Galaxy S I9000 Android Development] _JKay_:
So if the odex is in the /data/app folder then the apk will not be deodexed and put into cache? Sorry im still learning :-)
[Galaxy S I9000 Android Development] tonymy01:
Very nice mods, and fantastic to be able to quite intelligently do all the lag fixes from the recovery (including md5 checks before and after copy etc, very very polished for an alpha!!).

My first lag fix I have run admittedly, but this one seemed so polished after only 2 days out there, that I felt was worth a shot, and so far so good, an entirely different phone! (I am still subscribed to the Moto Cliq/DEXT support forums which is running hot right now due to the imminent Eclair release haha... but I am getting a 400 emails a day as a result of it, and this dragged the stock JP6 email client to its knees, now it has a new lease of life! Finally opening emails with 1meg jpg attachments isn't a "go and have a coffee while you wait" experience.

And I was investigating actually to put on the BLN kernel mods in the BLN thread (which was my primary aim for tonight's "tweaking"), and figured that I would miss out on the lagfix things by doing that, and stumbled across this thread with BLN as part of the tweaks, well done!!

Thanks again,

Tony
[Galaxy S I9000 Android Development] sztupy:
afaik only odex files in /system/app are considered. The odex files for the "simple" applications are stored in /data/dalvik-cache, and that's where android puts the results of it's odexing too.
[Galaxy S I9000 Android Development] RolluS:
Thanks for the explanation which also interests me, but then, why do rom-cookers provide deodexed and zipaligned rom?

On the first boot, it takes a long time to reodex all the apps isn't it?

I thought this time was taken too deodex the apps, and that deodexed apps run quicker than odexed ones...
[Galaxy S I9000 Android Development] xmonkee:
This is the greatest thing anyone had ever done in the history of dudes doing things. I would take my hat off to you, sir, but you seem like the kind of guy who likes his hats firmly on.
[Galaxy S I9000 Android Development] sztupy:
deodexed apps can run on any compatilbe firmware. Odexed apps can only run on one particular combination of the core android jar files. If using deodexed apps you can easily mod the core files or the application without the risk of it become unusable (because they will be reodexed to the new framework by android). Odexing is actually quite fast so you don't lose too much time with it.
[Galaxy S I9000 Android Development] RolluS:
Thanks for your answear.

I understand all now..

Odexing is done only once until dalvik-cache is cleaned.

Thanks a lot sztupy..
[Galaxy S I9000 Android Development] xtrememorph:
sztupy, instead of backing up and restore everytime file system is change, can there be an option to allow choosing a backup to be restored?
[Galaxy S I9000 Android Development] sztupy:
In the next version you can do the following:

- choose between "backup/restore" or "FR"

- chose FR, then the next reboot use nandroid restore with the one you desire.
[Galaxy S I9000 Android Development] xtrememorph:
Thank you very much :) btw what does FR stand for?

Also on JFS overkill without bind. When restore app from titanium it got the same app install lag effect as the OCLF. Voodoo5 does not have this problem. Could this be JFS limitation?
[Galaxy S I9000 Android Development] xan:
To anyone wondering about battery usage -> after 6h idle (data on, sync off) still @ 95%.

JFS on data, ext4 on dbdata, no loop. All tweaks active.
[Galaxy S I9000 Android Development] ragin:
@Sztupy,

I now have your Experimental 0.1 on, I want to try to install Docs v4 with your kernel, can I do this? Will there be any problem?

Please advice.

Thanks.
[Galaxy S I9000 Android Development] sztupy:
FR=factory reset (=clearing /data, /dbdata and /cache)
[Galaxy S I9000 Android Development] sztupy:
I don't know. Still have to find out why "installd" won't remove application data when using JFS.
[Galaxy S I9000 Android Development] KaliKot:
ahh, so thats what happened to me. it started lagging on apps again when I restored my titanium backup. Was frustrated and seriously wanted to sell it for an iphone cause of that
[Galaxy S I9000 Android Development] trasig:
hum. after trying to change from JFS avanced back to normal.. it seems stuck in a bootloop backing up data... it goes to maybe 70-80% and then just reboots. and restarts and tries backup again and restarts and so on..... soon filled whole sd with unfinnished backups erm :p so it never even comes to convert.

edit:

Seems its same file it tries copy that it hangs on each time.. maybe i shud just remove that file with adb before ;p

edit2:

bah. cant even boot into recovery mode anymore. only download mode. gaaaah. cant even restore my backup hehe
[Galaxy S I9000 Android Development] Cotw:
I noticed some bugs... I don't know if they're kernel-related or JP6-related.

-USB debugging is enabled al startup (noticed already noticed this).

-Time settings are set back to defaults (time zone 00:00).

Other than that great job :)
[Galaxy S I9000 Android Development] sztupy:
always enabled usb debugging is a feature :P (itás an alpha release you just want to debug it...)
[Galaxy S I9000 Android Development] zenkinz:
why don't you backup only partitions that require re-format?

for e.g. I wanted to try jfs only on /data, but end up with /data, /dbdata and /cache all backup, reformated and restore.
[Galaxy S I9000 Android Development] wangbin:
thanks a lot:):)
[Galaxy S I9000 Android Development] xan:
Well, I think its exactly what sztupy is talking about here
[Galaxy S I9000 Android Development] FadeFx:
always enabled usb debuging was fixed for me with 0.2, also i had the problem that my volume settings were always set to silent when i rebooted, this is also fixed with 0.2 for me. however, just could be that it goes to the settings like they were before install, have to test this...
[Galaxy S I9000 Android Development] sztupy:
For that I would need a more sofisticated algorithm. This one can usually handle all kinds of switches between two different state by doing a simple backup/restore for every partition.
[Galaxy S I9000 Android Development] trasig:
is there anyway to enable su from CWM? i need to run jfs_fsck. wich i cant do with /data mounted.. and cant unmount it when phone on (ofcoz).
[Galaxy S I9000 Android Development] sztupy:
debug mode is enabled, so you can run "adb root" to get root access for the next "adb shell" command.
[Galaxy S I9000 Android Development] mascian:
Hi sztupy,

First of all congratulations for your work: you have achieved an excellent result. Thanks! (ehm,..and sorry for my poor english).

But I would have a little problem ...: I use the DocRambone's rom (JP6 barebone + Stock android goodies, V3) and your kernel (V 0.2).

In the recovery I choose this scheme:

No-RFS Advanced JFS: all partitions are jfs (bind false, of course).

After rebooting I don't have more applications in / data, and to solve this problem I manually copied my applications in /data (obviously changing the permissions: rw-r--r--).

In this way, I solved.

But now I have a major problem: the system does not preserve custom settings after a reboot...You are already aware of this problem?

Thanks.
[Galaxy S I9000 Android Development] trasig:
any chance auto mounting of sdcard when pluggin in computer can be turned off? ;p
[Galaxy S I9000 Android Development] SLX69:
Looks great! Gonna try ASAP, thanks!
[Galaxy S I9000 Android Development] TeNdr:
BLN tweak is not working for missed call :(
[Galaxy S I9000 Android Development] xtrememorph:
Just some observation on advance JFS and ext4 with no bind using titanium backup.

JFS - Restore instantly and than system lag for program installation

ext4 - Restore slowly (restore screen stays longer) and than min lag

So both could be perform the same, just that the program check the file writing confirmation differently. JFS is journal first than write while ext 4 is the other way. So that would explain the situation above.

Quadrant give 1911 for ext 4
[Galaxy S I9000 Android Development] UnitySquad:
How do i enable led notification for ...?

* sms: notification by default

* touchwiz email: notification by default

* gmail: notification by default

* Google talk: notification by default

* call + calendar: download "Missed Call for Android 2.x" app (recommend)

-> configuration instructions for "Missed Call for Android 2.x"

* calendar: download "Calendar notifier" app from market (alternative)

* call: download "Easy reminder" app from market (alternative)

* any other apps not shipped with stock-samsung firmware:

ask the author of the app for notification led support
[Galaxy S I9000 Android Development] rugal28:
I can't use set cpu.....

kernel's problem? or my phone

maybe needs to flash the jpm again ~"~
[Galaxy S I9000 Android Development] uiterlix:
Thanks for this kernel, it's pure goodness. Finally one that incorporates both lagfixes and backlight notifications.

--uiterlix
[Galaxy S I9000 Android Development] kenkiller:
this kernel isn't made for OC-ing afaik. :D
[Galaxy S I9000 Android Development] sztupy:
Version 0.3

- before the lagfix gets applied there are now multiple options to chose from:

-- backup+restore (the original way)

-- backup, but don't restore (this eventualy results in a factory reset)

-- no backup (this also results in a factory reset)

-- go to recovery mode (to debug)

-- erase config file (to get back to the old options)

- the screen glitch in the first screen is now gone (because the kernel got smaller)

- jfsutils are ported to bionic (takes less space)

- there is a new option that will do the same restore permissions run, as the init script does

- I also added a few fixes to the CWM fix_permissions script, although I don't tested them yet (so it might brick the phone)

- Added two more rooting option:

-- the old one simply copyes busybox, superuser and su to the phone and adds symlinks to busybox

-- the new ones will also remove some old toolbox commands, so if you use the shell a lot, they won't interfere. The first mode only removes the base utils, like ls,mkdir,rm or ln

-- the second mode removes every toolbox command that has an equivalent busybox command (like mount, lsmod, rmmod, etc.)

Remarks

It seems that formatting dbdata as rfs only works, if you use the 512 PIT file (more exacty it only works if you have used the 512 PIT file the last time you've ticked re-partition in odin). This is probably due to the fact thet the 512 and 803 pit files reserve different space for the dbdata and for the system partition (the 803 pit file reserves 40 units less for the dbdata than the 512 pit file)
[Galaxy S I9000 Android Development] SLX69:
Just flashed and apllied the NO-RFS advanced JFS lagfix. I get a lower Quadrant than using the previous OCLF (1654 vs. 1854) although phone seems almost equally "speedy", so no problem. What I've noticed is that I cannot connect to my wi-fi router (wpa/wp2 psk), the phone gets stuck at obtaining the IP address, any idea?

Edit: BTW flashed 0.2 kernel
[Galaxy S I9000 Android Development] avary:
if i applied v2 over v1, should i apply lagfix again ?
[Galaxy S I9000 Android Development] _JKay_:
Wow. Its getting more and more complete. Great work. And fast progress.

Good to know about the pit files.

I still miss some benchmarks.

And I would like to be able to apply the fastest reading fs to /system partition.
[Galaxy S I9000 Android Development] trasig:
after installing superuser on this..when i adb shell.. no commands will work unless i type busybox ls etc... no way to bind the commands to busybox right away??

fixed.

had to copy /system/xbin/busybox to /system/sbin

maybe shud fix the symlink to /system/xbin/busybox instead
[Galaxy S I9000 Android Development] sztupy:
0.3 already has this options
[Galaxy S I9000 Android Development] UnitySquad:
I am using 0.2 with no rfs advanced jfs. Can i just disable the lagfix and update to your version 0.3? Thanks in advance
[Galaxy S I9000 Android Development] xan:
Just flashed 0.3 over 0.2 (dbdata=ext4 rest jfs) -> went smooth :)

So pretty much you dont need to disable lagfix before flash.
[Galaxy S I9000 Android Development] trasig:
well it binded to /sbin/busybox and not /system/xbin/busybox

so no commands worked before copying it..

and is there a way to turn of the auto mount of sdcard when cable in? its soooo annoying heh
[Galaxy S I9000 Android Development] efegue:
My card doesn't auto mount when I connect the cable. Btw, I use debug usb on.
[Galaxy S I9000 Android Development] batoo:
Cannot update to 0.3 via Odin, it hangs in 3/4 progress. It's ok with 0.2, any hint?

I use Advance All ext4 with JPM.
[Galaxy S I9000 Android Development] coine:
maybe a bug:

Market didnt work for me after 0.3 and lagfix "No-RFS Advanced: all partitions are ext4". When ill start to download an app it just stays downloading without any progress.
[Galaxy S I9000 Android Development] mat02:
Sztupy, what about voodoo sharpness and color correction (included in voodoo-pre6)? Can you add this as an option in your kernel?
[Galaxy S I9000 Android Development] mazdac:
@batoo:

check md5sum of Universal_lagfix_kernel_JPM_0.3.tar, should be

c4ff9edcc2f230c2aa5d32d98995bcd9, or simplier way.... just download it again.

I'm flashing using Odin under Windows on VirtualBox and works like a charm.
[Galaxy S I9000 Android Development] jogefo:
which rom has good speed/performane and good battery life with this kernel? I am using Tayutama's 1.0.1 and battery is not as great as the performance; I am on advanced Jfs
[Galaxy S I9000 Android Development] sztupy:
I try to only include options that can be turned on and off, although those modifications are nice. Maybe at a later stage.
[Galaxy S I9000 Android Development] TheTodFather:
This is looking so freakin sweet!
[Galaxy S I9000 Android Development] coine:
Any one else have problems with market after a lagfix of choice? Ive tried voodoo + No-RFS Advanced: all partitions are ext4 and i cant download from market. When i disable lagfix it works...

Ive also installed all the tweak options. But Market works when disabeling the current lagfix so i dont think that the tweak options are the problem.

sztupy, any idea?
[Galaxy S I9000 Android Development] sztupy:
for me a factory reset solved the issue. Unfortunately the logcat logs don't tell much when somethings wrong with the downloads. sorry.
[Galaxy S I9000 Android Development] Cbtg2005:
Could this be a general market issue, I've had this tonight myself. Everything was working fine, then I could download from market. I've even wiped the phone and reflashed to see if that fixed it as a factory reset wouldn't.

It would appear now that it is intermittent.
[Galaxy S I9000 Android Development] [Ramad]:
The market issue can't be fixed by factory reset, I have done that now several time with and without jfs, fixing permissions didn't help either; however, trying to download and cancel does help (you have to try many times)but the download speed is low compared to what it should be, nothing is wrong with wifi connection(tested with speedtest and was as it should be).

I Will report on jfs performance as it has been changed from last build (bionic now), will see if it's better.

Fixed from last build(0.2) is the minor corruption upon powering up.
[Galaxy S I9000 Android Development] mapas:
Can i flash just the kernel ? (not the whole .tar ?)

If yes how ?
[Galaxy S I9000 Android Development] xan:
Attached .tar files are kernels only, not a-firmware-package.
[Galaxy S I9000 Android Development] efegue:
I've tried with Advanced Ext4, JFS Overkill and Stock RFS and I can't download from the market, sometimes it works, sometimes not.. I don't think it's a problem with the file system!
[Galaxy S I9000 Android Development] fane1:
I was having the same problem with the market so i switched to ext2 and now it works :)
[Galaxy S I9000 Android Development] [Ramad]:
Have tested with stock froyo and market download issue is still there, so it might be that google is updating servers.
[Galaxy S I9000 Android Development] efegue:
looks like it's fine now :)
[Galaxy S I9000 Android Development] INeedYourHelp:
Hardcore updated his startup tweaks

It must be a pain to keep up with all the updates for all the lagfixes and other stuff.
[Galaxy S I9000 Android Development] sztupy:
0.3 already has the updated scripts ;)
[Galaxy S I9000 Android Development] avary:
im having market problem too, it keep saying start downloading and stuck there... i need run "cache cleaner" once or twice and then it works fine.

this less occur if downloading item is one or two, but if you press update all and has many programs to be updated and the same time, it stuck for sure .
[Galaxy S I9000 Android Development] INeedYourHelp:
damn, you're good.
[Galaxy S I9000 Android Development] guibao:
oh my... this is beautiful, awesome. so well documented

hope your project goes on on a fortunate and fast pace.

you should post your paypal account.

will try it soon.

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

edit: the paypal link is there already :D
[Galaxy S I9000 Android Development] Metalzoa:
I concur.

I'm about to get a Galaxy and Ive been lurking and keeping an eye on what the brilliant minds here have been doing.

If I ever feel my phone could use an upgrade, Im coming here because I like what I see.

Keep up the good work :)
[Galaxy S I9000 Android Development] avary:
applied v0.3 over v0.2, after reboot got alot of FC, too many. did a factory reset. restoring everything from titatium now .
[Galaxy S I9000 Android Development] ashwinds:
any changes to JFS in .3? Had issues with the Time getting reset on reboot (went back to GMT +0) and the issue of not being able to clear market data.
[Galaxy S I9000 Android Development] ashwinds:
Updated from .2 (ext4) to .3 (jfs) - _feels_ smooth ( i had a lot of lag with jfs last time) this time; market seems to be working just fine;

Time seems to be reset to GMT +0 again on each reboot though. Will check the rest and update if i notice any other issues.

PS: The old issue with being unable to Clear Data in applications still remains.. Going to try the untested Fix Permissions to see if it resolves it... gulp.

PPS: The new fix permissions didnt brick the phone as you feared it could, but still the time gets reset to GMT +0 and clear data still does not work :(
[Galaxy S I9000 Android Development] xtrememorph:
try to change pit to 512 done quite a few mistakes.. :(

Backup my file (still 0.2).. should have backup 0.2 and the update kernel than backup 0.3 than do repartition to 512 and than odin 0.3 and restore...

now after parition 512, have to use 0.2 first to restore 0.2 than update 0.3 than do 0.3 backup...

:( changing pit meaning previous backup wouldn't work...... somehow when backup i dont have dbdata.img :(

but somehow from pit 801 to 512 is ok
[Galaxy S I9000 Android Development] guibao:
Will merge this with Tayutama's and see what happens...

wish me luck!

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

edit

I replaced this zImage with the one inside Tayutama's Superlite 1.0.1 rom.

Booted to clockwork, did a factory reset, cleared the cache, selected the zip file and fired it up.

Everything went fine, I rebooted. While trying to get into recovery, I missed it around 5 times. I noticed that the reboot process became *very* fast,

even without a lagfix installed. Lockscreen became visible quickly.

Got into recovery, applied superuser, applied -ALL ext4-, restarted. It's all good.

Will check performance and post impressions.

Thanks sztupy, great job! :D
[Galaxy S I9000 Android Development] smacman:
Disregard.. Sorry.
[Galaxy S I9000 Android Development] zurchpet:
I almost cried from joy when I first time saw the speed.

I almost cried. It is blazing FAST! Finally the phone I wanted.

Thank you very much.
[Galaxy S I9000 Android Development] SLX69:
I just quote myself, sorry :-( Really nobody have a problem with wi-fi? just me?

Also noticed that the phone does not keep the timezone setting after reboot

Question for dev: if I disable the lagfix may I be able to use the nadroid backup to restore to my previous situation? Guess no because I think that nandroid does not backup the kernel, but not 100% sure about it
[Galaxy S I9000 Android Development] sunwee:
great job!

does this kernel includes mods from laststufo's Super Optimized JPM-JP6 Kernel?

http://xdaforums.com/showthread.php?t=811660
[Galaxy S I9000 Android Development] ashwinds:
I use wpa2 and it connects just fine. I have a problem with timezone too - i think it happens only with jfs.
[Galaxy S I9000 Android Development] SLX69:
Thanks for the info, guess it's just me :-(

Will apply v.0.3 later and see if that helps, if not it's time for a full Odin reflash again :-(