If anybody here doesn't mind testing, could you check out the following thread and test the new z4mod app on your Vibrant? I only have an I9000, but the app (and lagfix) should work fine on the Vibrant as well. Let me know please!
http://forum.xda-developers.com/showthread.php?p=9307467#post9307467
Awesome, Thanks Ryan! Downloading now, will report.
Update: Stock JK2 kernel patched fine but the conversion to ext2 did not work.
testing...........
Whitehawkx said:
Hey Ryan,
I patched the stock Vibrant JK2 kernel and it patched successful, however the conversion to ext2 did not work. Said it worked, rebooted, but I was still on RFS.
Click to expand...
Click to collapse
Quote above from i9000 forum, but thought I should reply here since this is for Vibrant.
Same for me. I am on a Vibrant Running TW Obsidian V3.1, stock kernel. Uploading my kernel, patching & redownloading all seemed to work. Selected convert filesystem, the app said it was copying files, etc., and rebooted. App still says FS is RFS after reboot, and Quadrant score is the same. Maybe doesn't work with this ROM?
Also, I was surprised there was only an option for ext2. I thought the point of z4mod was to use ext4 or some other format. I apologize if I am mistaken. Thanks for all your hard work! OCLF app is great.
justingriff said:
Quote above from i9000 forum, but thought I should reply here since this is for Vibrant.
Same for me. I am on a Vibrant Running TW Obsidian V3.1, stock kernel. Uploading my kernel, patching & redownloading all seemed to work. Selected convert filesystem, the app said it was copying files, etc., and rebooted. App still says FS is RFS after reboot, and Quadrant score is the same. Maybe doesn't work with this ROM?
Also, I was surprised there was only an option for ext2. I thought the point of z4mod was to use ext4 or some other format. I apologize if I am mistaken. Thanks for all your hard work! OCLF app is great.
Click to expand...
Click to collapse
I was running it on stock rom so I'm betting it's strictly a coding issue. As for ext2 being the only option I believe it's b/c that is all the stock kernel supports. Someone correct me if I'm wrong...
Whitehawkx said:
I was running it on stock rom so I'm betting it's strictly a coding issue. As for ext2 being the only option I believe it's b/c that is all the stock kernel supports. Someone correct me if I'm wrong...
Click to expand...
Click to collapse
Correct. I think stock also supports ext3 also
Tested on stock 2.1 ji6, Error: Cannot patch kernel.
Worked perfectly on stock 2.1
Tested on TW 4.2 ULF with Eugene's A12 kernel... couldn't convert...
Tested on Eugene stock Froyo build and it works...
Worked like a charm Ryan! I had to root phone again due to a soft brick last and your Z4root got me rooted quick and easier than the previous method I used. Thanks!
Didn't work for me, on stock 2.1 (ji6). It would only reboot into recovery after patched kernel was applied.
Does it work with Froyo?
Also how different is it from the Universal Lagfix that team whiskey has?
hanbaoquan15 said:
Does it work with Froyo?
Also how different is it from the Universal Lagfix that team whiskey has?
Click to expand...
Click to collapse
Yes it works with Froyo. This is an app that patches the kernel, not an entire kernel replacement like the ULF. This is a bit less invasive because any future kernel changes from Samsung won't require a reflash. On the other hand, ULF has far more options (including formatting more than just /data and your choice of file systems -- although z4 has stated RyanZA will add these options in future releases)
I want to convert all of /System.
Thanks
Gave it a shot. Uploaded kernel, patched it, downloaded it, rebooted to flash kernel, but doesn't seem to flash it. Every time I reopen the app it wants to try flashing it again. Is it just a CWM .zip that I can flash manually, and if so where can I find it?
I'm running Macnut R12 with stock JK2 kernel.
budney said:
Didn't work for me, on stock 2.1 (ji6). It would only reboot into recovery after patched kernel was applied.
Click to expand...
Click to collapse
Nope -- doesn't work. What's the simplest way to fix this?
It seemed to patch the stock JK2 froyo kernel, but the filesystem would not convert to ext2...
legit mod!
scrizz said:
I want to convert all of /System.
Thanks
Click to expand...
Click to collapse
That won't do anything as /system is read-only. The lag comes from writebacks.
If we unroot with z4 with the phone flashed with a rom will it brick?
Sent from my SGH-T959 using XDA App
Related
A lot of ROM developers are using Gumbo's Custom Kernel but when i install it i always get a bootloop. ALWAYS! i have tried almost everything: COMPLETE wipe and flash, and even repartition.
I am running Modaco 2.2
andyandrwew said:
A lot of ROM developers are using Gumbo's Custom Kernel but when i install it i always get a bootloop. ALWAYS! i have tried almost everything: COMPLETE wipe and flash, and even repartition.
I am running Modaco 2.2
Click to expand...
Click to collapse
We can't really help you unless you give more info, what does you logcat say?
got it!
it was because i had ext4
this is because Modaco has ext4 enabled and Gumbo does not.. so hence it locked up..
EXT4 is NOT widely used yet. Highly experimental...
At the risk of asking a stupid question, whats the difference between ext2, 3, and 4? I think I'm using 3. I havent gotten around to bringing one of my comps here from my other house to start running linux, so I haven't adjusted to the OS yet.
Hey folks, so here's a basic summary of what I've done up to now...
Rooted... have Rom Manager, etc...
Flashed JH7 OTA with Clockwork. Worked nicely. Set some things up, happy at this stage so I made a backup.
Decided to try Cognition, was 2.1.4. Had some trouble with a few things.
Disabled lagfix, simple enough.
Flashed to a backup made when I was on regular JH7.
So to the question... when I go to About in Settings, my Kernel still says
[email protected] #Voodoo_lagfix_3.0_v1.9.
Shouldn't the Kernel have converted back when I restored/flashed my backup?
Clockwork won't reflash your kernel (unless it's a package with included kernel) however the voodoo kernel you currently have on your phone operates the same as a stock kernel until you remove the disable-lagfix folder. Cognition 2.1.4 does utilize that version of the kernel to enable init.d scripts for things like MobileAP to function
You just have all the answers don't ya?
Thanks again, really appreciate it.
maximus-dev said:
You just have all the answers don't ya?
Thanks again, really appreciate it.
Click to expand...
Click to collapse
Haha I do my best to stay informed around here
OK. I've been asked to create a new thread so I can update the OP with the latest info, so here we are.
First off, if you currently run voodoo, or any other lagfix, YOU MUST DISABLE IT.
DON'T FORGET TO BACKUP YOUR DATA. We make an effort to backup for you and restore, but it's entirely possible that the process will lose your data or otherwise break things. I recommend Titanium Backup for apps/data, please only backup/restore user apps/data with Titanium. System level stuff sometimes doesn't restore properly, causing FCs and other errors.
Now, install the kernel.
http://www.tabbal.net/files/Kernel-ttabbal-v1.7.zip
REBOOT. The z4mod will not install properly if you are not booted into one of my kernels.
Now you can install the z4mod. Reboot into STOCK recovery, then select "Reinstall Packages" to get to clockwork. Now you can install the ZIP below. DO NOT INSTALL FROM ROM MANAGER. It will work, but /cache can't be dismounted if you do it that way, so you can't convert it.
http://www.tabbal.net/files/z4mod-ttabbal-ext4-v1.5.zip
If you want to get back, which you need to do to convert between ROMS and such, here's the revert script.
http://www.tabbal.net/files/z4mod-ttabbal-rfs-v1.5.zip
Tested on Bionix Final and Fusion. Reports of it working on Eugene's ROMS and JI6. Note that if you want to run JI6, you need to install the kernel backport package from Eugene here.
http://forum.xda-developers.com/showthread.php?t=796425
FAQ:
Q) Can I run z4mod with JAC/KK/JI6/Stock Kernels?
A) NO. The kernel has to be modified to work properly with z4mod. So far, I have been unable to build JAC/KK kernels from source. Someone did manage to modify a stock JI6 kernel, but I am unsure of the results. If it has been confirmed, I will add a link here.
Q) What do I need to do to flash a new ROM?
A) Convert back to RFS with the RFS zip above.
Q) I get errors in Clockwork when trying to flash ZIPs.
A) I'm working on that. The workaround for now is to use "adb shell" to mount the partitions manually. Then it will work. The exception is a full ROM flash. You must revert back to RFS for those.
Q) Why bother? VooDoo, OCLF, etc. already exist.
A) z4mod has more potential. We can convert just about any partition to use whatever filesystem we want to. Voodoo and OCLF are limited to /data. The same tricks could be used to convert others, but z4mod is a cleaner design which makes doing that easier.
Thank You
Thanks for taking the time to build a Kernel for the Vibrant that will work with the Z4mods. It was starting to look like no devs were going to work on this Lag Fix mod for the Vibrant!
By the way, have had installed for a week now and everthing is working great, and I'm really digging the Backlight notification built in!
Running Bionix 1.1 with
Ext 2 for Data, DBdata, Cache, and System! No more RFS!
When you say "The exception is a full ROM flash" do you mean that a full ROM flash will not have any problems flashing from CWM after reverting back, or is it still necessary to do an adb mount?
Thanks a lot for the new thread. Much more organized.
Thanks for creating the new post...I was going to post this today as well
The 1.7 kernel version is working perfectly on my Bionic Fusion rom.
Appreciate all your work.Hopefully more people will try it out now...
Sent from my Galaxy using Tapatalk
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
jdkackley said:
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
Click to expand...
Click to collapse
I think he is working on that.
bstromberg said:
When you say "The exception is a full ROM flash" do you mean that a full ROM flash will not have any problems flashing from CWM after reverting back, or is it still necessary to do an adb mount?
Click to expand...
Click to collapse
For a full ROM flash, you must flash the RFS ZIP file, reboot to recovery, then flash the new ROM. The reboot is important, don't skip it.
Wow, thanks for starting this up anew.
Is there a way to convert /cache or others? Any caveats to converting other partitions?
Wow, this is like night & day compared to stock & feels a bit faster than Voodoo.
I did a fresh install of Bionix (older version with voodoo) and played with it & then did a fresh install of Bionix (same version, stock kernel) and then flashed z4 on top of it & it still feels a bit snappier.
I did that so I could get a feel for the differences between it & voodoo (non-scientific).
I'll probably finally upgrade to Bionix Fusion 1.1 with this kernel since it doesn't offer voodoo anymore & this actually seems faster than voodoo for me.
THANK YOU FOR THIS!
Kubernetes said:
Wow, thanks for starting this up anew.
Is there a way to convert /cache or others? Any caveats to converting other partitions?
Click to expand...
Click to collapse
For me, it converted
/data
/dbdata
/cache
tjhart85 said:
Wow, this is like night & day compared to stock & feels a bit faster than Voodoo.
I did a fresh install of Bionix (older version with voodoo) and played with it & then did a fresh install of Bionix (same version, stock kernel) and then flashed z4 on top of it & it still feels a bit snappier.
I did that so I could get a feel for the differences between it & voodoo (non-scientific).
I'll probably finally upgrade to Bionix Fusion 1.1 with this kernel since it doesn't offer voodoo anymore & this actually seems faster than voodoo for me.
THANK YOU FOR THIS!
For me, it converted
/data
/dbdata
/cache
Click to expand...
Click to collapse
Awesome. Silly question, but what do Quadrant scores look on this? I'm curious because database writes should be super fast with this, right?
jdkackley said:
ttabbal,
Does this have overclocking capabilities as well? I didnt see any mention of it in the OP.
Click to expand...
Click to collapse
No OC/UV. Personally, I don't miss the OC, it's that smooth with z4mod. I am looking into adding it, but hope to just work more closely with Team Whiskey to add it to their kernels as they are way ahead of me on OC/UV stuff. There's no point in everyone working on the same stuff. And if they handle the main kernel I can concentrate on other stuff.
I will try this when I can use other kernels.
ttabbal said:
No OC/UV. Personally, I don't miss the OC, it's that smooth with z4mod. I am looking into adding it, but hope to just work more closely with Team Whiskey to add it to their kernels as they are way ahead of me on OC/UV stuff. There's no point in everyone working on the same stuff. And if they handle the main kernel I can concentrate on other stuff.
Click to expand...
Click to collapse
Thanks for the quick reply! And I totally understand what you mean about everyone doing double work. There is no need for that. You guys all have enough that your working on.
I do have another question if you dont mind. Does this kernal affect either negatively, positively or nochange over stock, the battery life of the phone? The only reason why I ask is that I have noticed an increase in battery life for my phone while running VooDoo with JAC's OC/UV kernal. If no one has tested this at this point I am willing to flash it and give it a go and report back. But I just thought that if someone already has, then there is no point in me doing double work as well. As the battery life is what I really like about JAC's kernel. Thank you in advance! And just for the record this looks to be very promising in the future. Maybe if JAC is out there looking over any of this thread, hopefully he can chime in and provide us all with some insight or help. Thanks again Ttabbal! Great work!
Kubernetes said:
Awesome. Silly question, but what do Quadrant scores look on this? I'm curious because database writes should be super fast with this, right?
Click to expand...
Click to collapse
I have Data, Dbdata, cache, and System all converted to EXT 2 with the Z4Mod and my quadrants are around 1800. This lagfix is much faster than any lagfix to date whether you use EXT 4 or EXT 2.
The UV/OC really doesnt matter with this mod, but of course it could only get better when that is implemented.
Works Great! Thanks!
Followed the instructions and everything worked like a charm. Converted /data and /dbdata to ext4 and /cache to ext2. Ran Quadrant and got a score of 1621. Everything seems very snappy and smooth. Overclocking would be nice, but isn't really necessary. Great work ttabbal! Thanks!
dsellers2 said:
I have Data, Dbdata, cache, and System all converted to EXT 2 with the Z4Mod and my quadrants are around 1800. This lagfix is much faster than any lagfix to date whether you use EXT 4 or EXT 2.
The UV/OC really doesnt matter with this mod, but of course it could only get better when that is implemented.
Click to expand...
Click to collapse
I was getting 2100 with lagfix from TW's website. Then I OC'd.
jdkackley said:
Thanks for the quick reply! And I totally understand what you mean about everyone doing double work. There is no need for that. You guys all have enough that your working on.
I do have another question if you dont mind. Does this kernal affect either negatively, positively or nochange over stock, the battery life of the phone? The only reason why I ask is that I have noticed an increase in battery life for my phone while running VooDoo with JAC's OC/UV kernal. If no one has tested this at this point I am willing to flash it and give it a go and report back. But I just thought that if someone already has, then there is no point in me doing double work as well. As the battery life is what I really like about JAC's kernel. Thank you in advance! And just for the record this looks to be very promising in the future. Maybe if JAC is out there looking over any of this thread, hopefully he can chime in and provide us all with some insight or help. Thanks again Ttabbal! Great work!
Click to expand...
Click to collapse
I'm also wondering about battery life. That's the only reservation I have about the kernel required for this lagfix. I have been getting horrible battery life recently even though I've conditioned and all that jaz. So I'm a little worried about it.
I hope everyone understands that I'm not really concerned about the actual overclocking as much as I am with the undervolting of the CPU at midrange speeds. Strictly for battery life. I am completely aware of the benefits of converting the filesystem to extension 2/3/4 and do realize that this will greatly enhance the speed of the phone. I just wanted to be clear. And I am in no way trying to give anyone any type of attitude or imply any type of flaming what so ever. Thank you all for sharing your experiences.
When I went to install the z4mod it completed in like 3 seconds but in the text it says "This WILL take awhile". I'm wondering if I did it right, I followed directions in OP completely. I'm running JI6.
Edit: Also for some reason It wont allow me to install anything from the market, so, I probably screwed something up. Not sure how tho.....
I seem to have a recurring problem with my root on the FireFly 2.8 rom, though it may have been present on Serendipity and I never noticed.
My problem is this: Before I flashed FireFly, I used Odin to revert to stock 2.1, master cleared, and then rooted using the One Click Galaxy S root, which worked fine. I was able to flash the rom using CWM and Titanium Backup as well as other apps that require root said they had proper permissions.
At some point, I do not know where, I lost my root. Now, when I try to use Titanium Backup or Firefly fixes, the app tells me Root access FAILED.
I have superuser as well as the current busybox. Can anyone help me with possibly telling me how to enable my root or how to reroot if necessary?
I have tried z4root but it never does anything anymore.
And when I try to use the One Click Root again I can not click "reinstall packages" because I am taken to CWM instead of regular recovery.
Any help would be appreciated, thank you.
You probably converted system to ext4. Go back into Recovery and go to the features of whatever kernel u are using and reapply root.
Sent from my Captivate running Continuum 4.0 with Onix 2.0.5.
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
#1 in CWM "reinstall packages" is the 2nd option down! called "apply update.zip" (kinda makes sense doesnt it?)
#2 if you have CWM you can root without one click root.
boot to CWM recovery> Clockwork Features > root + install superuser
adv
Edit: Nevermind, looks like someone already solved your problem while I was typing my BS out.
skrallbro said:
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
Click to expand...
Click to collapse
You don't normally have to....
I has this same problem with FireFly 2.8. I never had that issue with older versions of FF. But, as mentioned, if you reapply root in CWM, it works again.
I love the FF themes, and stability, but I may go back to FF 2.6. FF 2.7 had charging death for me, and FF 2.8 I have issues with keep the lights on. That's how I found my root issue. Now, with the root fixed, keep the lights on seems to disable itself after a while. Definately after every reboot it turns back off. I never had this issue before with cog, perception, or any of the earlier FFs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Elisha said:
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Click to expand...
Click to collapse
All the FireFly versions I have used have the lagfix optional, and applied through CWM, but 2.8 is the first one that applying the lagfix affected the root of the ROM. I also didn't have this issue with Cognition or Perception, both of which apply the lagfix on first boot.
So the kernel is the issue, not the ROM? A different kernel may fix this?
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
So the kernel is the issue, not the ROM? A different kernel may fix this?
Click to expand...
Click to collapse
Yes and no. losing root from converting system to ext4 or back to rfs, can happen with any kernel, and for the charge death that was the onix kernel in those versions. The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
i have never lost root converting my system
but i havent converted it in over a month. Just leave it EXT4 when i upgrade/change roms.
havent had any problems not converting it so i dont bother. (except going to stock)
but when i used to convert back and fourth every flash out of fear... NEVER LOST ROOT
I've only lost root converting on Continuum but never on FireFly or Apex so not sure if it is kernel or rom.
Sent from my GT-I9000
studacris said:
The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
Click to expand...
Click to collapse
Yes FF 2.8 has bln options in CWM. I have issues with bln active or disabled (in FF 2.8). I have not tried managing the bln with the app from the market, would that make a difference (vs managing bln in CWM)?
Sent from my SAMSUNG-SGH-I897 using XDA App
Few minutes ago, I flashed my SGS I9000 with webstar1's Ultimate ROM http://forum.xda-developers.com/showthread.php?t=854799, everything's going fine, and i'm pretty much satisfied with the functionality and such.
However, when i ran a speed check with Quadrant Standard, it shows that my speed is benchmarked at 1100. Before i used this ROM (was using stock), it was at 1700 with voodoo. Right now, voodoo is disabled because I created the disable_lagfix folder. Is it possible for me to enable voodoo? Or will it create some clash with the ROM itself and cause troubles to my phone?
Thanks for any help/advices that any experts could clarify, cheers.
Re-enable the lagfix by deleting the file. No, there shouldn't be any issues. This would however work if you're once again on the Voodoo kernel after flashing the new ROM. If you're not, flash that first.
And for the record, Quadrant doesn't mean squat!
Does that mean i should flash the voodoo kernel first, without remove the disable_lagfix folder? Or i should try removing the folder, and if any problems persist, then flash the kernel? If i feel that the experience using the ROM is smoothe, i shouldn't enable voodoo anyway i guess..
EDIT: I just notice the ROM comes with a kernel made by DamienGTO. Does that mean i have to re-flash the voodoo lagfix? Thanks for the help though, much appreciated!
aksyong said:
Does that mean i should flash the voodoo kernel first, without remove the disable_lagfix folder? Or i should try removing the folder, and if any problems persist, then flash the kernel? If i feel that the experience using the ROM is smoothe, i shouldn't enable voodoo anyway i guess..
EDIT: I just notice the ROM comes with a kernel made by DamienGTO. Does that mean i have to re-flash the voodoo lagfix? Thanks for the help though, much appreciated!
Click to expand...
Click to collapse
It wouldn't matter either way. The lagfix would only activate on Voodoo kernel with the disable file/folder removed.
EDIT: DamianGTO's lagfix implementation is different, I believe. The Voodoo folder would have no significance when on that kernel. I would suggest you to stick with the new kernel over the basic Voodoo one. You can activate lagfix from CWM Recovery.