Related
THIS IS FOR CAPTIVATE ONLY
I am not responsible for any damage caused to your device
BACKUP BACKUP BACKUP with Nandroid and Titanium Backup before installing this.
What this is:
Voodoo lagfix beta 4 from supercurio
Backlight notification patches from neldar
Vanilla Captivate kernel built from Samsung sources.
What this is *not*:
Unhelpful OC/UV kernel. I did start from his github repository, and cherry picked the changes I wanted while leaving the OC/UV out for now.
Voodoo color fix.
How to install
Download captivate-voodoo3.0_bln_v1.10.zip. (You can also install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip if you do not want backlight notification).
Did I say backup first yet? Backup in case something fails and you need to recover!
Rename the downloaded file to update.zip, put it on the root of your built in sd card (not the removable one!), reboot into stock recovery mode, select reinstall packages. The first conversion takes a long time depending on how much data needs to be converted (the white AT&T screen). The phone will tell you as it progresses through the different stages ("please wait", "step 1", "step 2" and if all goes well "conversion successful"). Important: You have to install via recovery using the update.zip if you want the backlights to work because this also needs /system/lib/hw/lights.default.so to be updated for BLN support. Either that, or install the file yourself by pulling it out of the update.zip and putting it in /system/lib/hw, overwriting the stock version. If you do not want backlight notification, install captivate-voodoo_lagfix_3.0_v1.10_nobln.zip instead.
Important
If you have installed v1.2 or below or installed v1.4 or installed v1.5 while I had it up, you need captivate-voodoo-beta4-v1.5a.zip to clean up the sound configuration first. Then install the latest release. You do not need v1.5a if this is the first time you are installing this (or are coming from stock), you just need the latest release.
Nandroid, ClockworkMod
Disable the lagfix as above before using Nandroid, Clockworkmod because they do not understand EXT4 yet and will not backup correctly.
More details on the voodoo lagfix on http://project-voodoo.org/installation as it is basically the same as the Galaxy S (international).
Enjoy!
HSUPA (optional, bluetooth mic does not work):
Install Captivate Voodoo+BLN+HSUPA kernel+ I9000 JH2 modem: Before you flash this, first install the Captivate Voodoo+BLN kernel above. Then use ROM Manager to flash i897_hsupa_v1.10.zip. This will install a new Captivate Voodoo+BLN+HSUPA kernel that allows us to use the I9000 JH2 modem that enables HSUPA for us. There is no need to disable-lagfix if you already have Voodoo lagfix working, but it is a good idea to make backups in any case. Note: Bluetooth mic does not work with this yet.
Revert back to Captivate Voodoo+BLN+JH7modem:
Use ROM Manager to flash i897-captivate_v1.10-revert.zip. This will flash back to the Captivate Voodoo+BLN kernel without HSUPA and will also flash the Captivate JH7 modem. No need to disable lagfix if you are already running it.
Uninstall:
Disable lagfix
1. Mount phone on computer (connect it so that you see its two card, one internal, one external if you have one).
2. Navigate to the Voodo folder on the internal SDCARD (there should be only one of the two cards that has this folder)
3. Create a file (or folder) named "disable-lagfix", no extensions. (right click -> new-> new file or folder)
4. Unmount your cards from the computer.
5. Shut phone OFF.
6. Turn back on.
You should hear the "Converting EXT4 back to RFS".
Scary way to get original kernel back
If you really really want to go back to the kernel you had before applying the lagfix kernel (why?), first disable the lagfix as explained above. Then you will need to get into adb shell, with root.
Code:
thor$ adb shell
$ su
# redbend_ua restore bml7-zImage-kernel-backup.img /dev/block/bml7
Be very very careful with this command. If you make a mistake, you can brick you phone for good.
If *I* wanted my original kernel back, I would just disable-lagfix, make a backup and then use Odin One-click to go to stock and then restore from backup. Much less scary and no danger of killing the phone.
Changelog:
1.10 Added backlight notification. Changed to use stock sbin/init because the previous init might have been the cause of some ppl losing sdcard or usb (might have been!). captivate-voodoo3.0_bln_v1.10.zip captivate-voodoo_lagfix_3.0_v1.10_nobln.zip
1.9 Same as 1.8, but with a different method for handling init.d scripts so it uses the standard busybox run-parts. captivate-voodoo_lagfix_3.0_v1.9.zip
1.8 Make sure /data is mounted noatime, nodiratime - better performance and fewer writes to flash. Was an oversight that these were dropped. captivate-voodoo_lagfix_3.0_v1.8.zip
1.7 Cleaned up /system so nothing is left there after the phone comes up fully. No change in behavior. captivate-voodoo_lagfix_3.0_v1.7.zip
1.6 Clean voodoo installation with stock Captivate kernel (actually the same as v1.3, but to avoid confusion for ppl coming to this from stock). captivate-voodoo-beta4-v1.6.zip
1.5a Bugfix release that cleans up the mess from any previous voodoo installs that disabled sound for you. captivate-voodoo-beta4-v1.5a.zip
1.4 There is no 1.4 anymore. If you installed it, you need 1.5a above.
1.3 Fixed headphones problem (configuration problem for sound in general) captivate-voodoo-beta4-1.3.zip
1.2 Added init.d support to allow things like mobileAP etc to work. Do not use.
1.1 Totally vanilla update.zip - has nothing but lagfix. Do not use.
1.0 Left some pieces from my SRE installation on the update.zip - fixed in 1.1
Credits:
Francois Simond, supercurio on XDA (Voodoo lagfix)
[email protected] (Backlight notification patch)
[email protected] (kernel help)
Github repositories:
Voodoo initramfs used to build the kernel initramfs
Linux kernel sources, configs for Captivate to build this release
Toolchain used
Clone the repos, change the CONFIG_INITRAMFS_SOURCE to point to the voodoo initramfs in the i897_defconfig file under arch/arm/configs of the kernel and build with the build_kernel.sh in the top level of the linux kernel directory. The build_kernel.sh has to be edited to change CROSS_COMPILE to point to the toolchain and the AOSP variable has to point to the place where it can find the signing tools under the eclair build from AOSP.
Donate:
I am a liver transplant survivor and I would not be here if not for the generosity of the person who was thoughtful enough to have signed up to donate his organs before he passed away.
And if you are feeling cash rich, you could also support supercurio for the voodoo lagfix and support neldar for the backlight notification. I have tried to keep the kernel as vanilla as I could so that I could isolate the changes to just the ext4 lagfix. I will include more things as I work on this and if I have the time!
I am putting everything on github so others can continue on this if I am lax
-Atin
oooo nice! 10 chars
my sweet jebus yes
Installing now. Lets see what all this talk has been about.
My phone is talking to me!
Great. Another reason to flash. Thanks. )
Sent from my f5 hitter.
GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?
DOAlaboratories said:
GOD DAMMIT! literally 5 minutes after i flash SRE this comes out. how should i flash over, just head back to stock?
Click to expand...
Click to collapse
you can flash on top. you'll lose some of the things from SRE until I have the two merged fully.
Should I just Odin myself back to stock then do this or will it work over my root, lag fix, etc?
After a really bad experience with SRE and sleeping death, this is much needed. Thanks much
Ah.. so this is where everyone seems to be tonight lol.. going under my USER CP i see the vanilla/SRE/Capti-VibHybrid always refreshed!
Great to hear this I'm excited to see if anyone finds poquito bugs!
I just flashed this on top of SRE running jH7 and my
Phone is talking to me while
It's on the Att white screen! Crazy but it's sexy ahahahA
why not have this simply as a lagfix, and incorporate it into SRE, instead of trying to make yet another all-in-one tool?? It will be nice to just have one tool (SRE), and have the voodoo lagfix incorporated into that instead of the other way around.
Oh and btw, if you do incorporate unhelpfuls oc/uv kernal...PLEASE keep a version with stock clock speeds/voltages. Some of us have no desire for this, and as of now, it seems to be the source of most of the problems.
I have one request. I see that u are planning to incorporate oc/uv in this mod. Can u make a non-oc/uv version as well? My experie ce with it has been nightmarish
Just finished!
Got 1533 quadrant score with all my stuff intact. No fresh install! Loving this so far!
Edit: ran quadrant second time and I got 1785
Hey, looks like someone stole my thread layout... pshhhhh
this is going to be in SRE
the fix, not this...
designgears said:
Hey, looks like someone stole my thread layout... pshhhhh
Click to expand...
Click to collapse
I thought I felt strangely familiar reading the OP.... lol
Can we get a lagfix only update like on the main voodoo page? This one messed up my theme and that's gonna be a deal breaker. lolz jk
EDIT: Ahhhh and removed my overclock!!
wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
ha, and this is the I9000 kernel, its not even for captivate.
designgears said:
wow, just downloaded the zip, not very happy about this...
that is SRE with a few edits to add voodoo...
shame on you
THIS IS SRE WITH VOODOO
Click to expand...
Click to collapse
first the thread layout, and now SRE! You should take this as a compliment, that means you are doing something right!
wow really DG?! dang .. something is very wrong with this IMO. :/ .. is this going to be another cyanogen type drama Dx ..
at least he mentioned your name in credentials..
lol it's written designgears(SRE) .. it's openly written he literally used your code .. X__x.. not as bad as the cyanogen drama.. D: .. >_>..
am i making this too dramatic than it is o_o?
1726 quadrant and no sleeping death yet. Im keeping a copy of this version
I installed the bionix 1.5 today (Bionix 1.5 w/JACs OC/UV/VOODOO Kernel). I have not installed any lag fixes before. The install went great, but my quadrant score is still 1300. I do not have the "disable-lagfix" file on my sdcard. The Voodoo directory has but one subdirectory - "logs". I looked through the logs, and it looks like things are happening. The phone is running fine, but I just wonder if the voodoo lag fix is actually doing anything. The mount command does show /dev/block/mmcblk0p4 /data ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
So, is it working???
Cheers!
Skip
MrGibbage said:
I installed the bionix 1.5 today (Bionix 1.5 w/JACs OC/UV/VOODOO Kernel). I have not installed any lag fixes before. The install went great, but my quadrant score is still 1300. I do not have the "disable-lagfix" file on my sdcard. The Voodoo directory has but one subdirectory - "logs". I looked through the logs, and it looks like things are happening. The phone is running fine, but I just wonder if the voodoo lag fix is actually doing anything. The mount command does show /dev/block/mmcblk0p4 /data ext4 rw,noatime,nodiratime,barrier=1,data=ordered 0 0
So, is it working???
Cheers!
Skip
Click to expand...
Click to collapse
Yes it is enabled, and you are under ext4. I wouldnt read too much into quadrant scores and other benchmarks, voodoo is the way to go. Dont be fooled into using those other adb shell ext2 lagfixes for benchmark scores, theyre unstable and are prone to data corruption.
Thanks! That's what I was hoping.
I flashed with the same ROM today and my 2200 quadrant score went down to 900....still trying to figure out what happened. I don't care, but it's a nice to know scenario.
darquegt said:
I flashed with the same ROM today and my 2200 quadrant score went down to 900....still trying to figure out what happened. I don't care, but it's a nice to know scenario.
Click to expand...
Click to collapse
open a terminal and type 'mount' - look for the /data partition. If it's mounted ext4, the lagfix is applied. If it says RFS, you are likely in the same boat as me. You are part of the small percentage of people with a different NAND chip than the rest. Voodoo beta 4 does not support it, wait for beta 5. On the bright side, from what I've read, it also means I have about 500MB more storage than everyone else
I did the manual lag fix and quadrant scores went up to 2400 (about 200 above the previous score on the factory ROM without the OC). The biggest gain was at the DB writes.
Thanks time killer, do you know what that percentage is?
Seems like I don't get voodoo for now either.
A there any other good/bad news about the small percentage?
"...the best choice for a custom ROM on the Captivate" - AndroidCentral
Number One In Random And Plausibly Flawed Battery Testing By Random Persons
6.4
Added 2048 SD Card Script
Added Ram Booster Script
Added Permissions Fix Script
Updated Market
UI Tweaks
SERENDIPITY WEBSITE
A few words about the Optional But Totally Awesome Steam Kernel
Ok, so hopefully you read a bit about it in SzutpY's post. I compiled Steam recovery in English and made a kernel utilizing it. The kernel is similar in many ways to the Universal Lagfix Kernel SztupY also created. It has many of the same lagfix schemes, kernel tweaks, etc, again, all with a touchscreen interface. Other than Steam recovery, this kernel is identical to my 12-23 oc/uv kernel, so it's overclocked, and undervolt configurable, and it should be just as stable as that one.
Do not attempt to take the zImage with Steam recovery and place it in a flashable zip. You'll be a sad panda if you do. I'd advise waiting a few minutes after your system has booted to flash with Neldar's app. If you're using Odin, or Heimdall, reboot to download mode and flash like normal. Those are the options, either Neldar's app (AND NOT Tuxility!!) There are issues with flashing this via redbend_ua - the regular kernel can be flashed via redbend_ua, Steam cannot be.)
Steam recovery is based on ClockworkMod, but you have a touchscreen interface at recovery. Steam has many options to lagfix your system. So, you can have an all ext4 system (including /system), an all jfs system (again, including /system) or something in between. Read through sztupy's posts about Steam, or spend some time playing with it. I have to admit I was a little skeptical of it at first, but after using it for the last week or so, I absolutely love it.
If you're doing a filesystem conversion from Steam recovery, the zeroth thing you should do is check to make sure you have enough room on your SD card to copy /system, /data, /dbdata, and /cache. Then, make a backup. Occasionally after a filesystem conversion, the system will bootloop. Performing a three button forced reset and rebooting solves this. (In my experience at least. Like I said, make sure to backup first.)
If you do choose a No-RFS lagfix in Steam - Make sure you disable it before flashing another kernel/ROM. No-RFS uses a fake /efs to get a completely-rfs free ROM (only works if /system is set to be mounted as rw).
If it seems as though you've lost su (root)
So, I don't know why Steam does this, but the reason people were losing su was because it was automatically mounting /system nosuid. So, to fix this, there's probably more than one way to do this, but an easy way is to go into Steam, under boot options, select 'Always run adb as root' or something like that. Then reboot, open a terminal and type
Code:
mount -o remount,suid /dev/block/stl9 /system
. That will remount su access to /system (pretty important ), and then you will have root again, and Steam is finally usable again. Flash another kernel or whatever) I was really hoping I could blame this on something MikeyMike did, hmm...I may still find a way. ( Alternatively, it seems if you do a filesystem conversion on /system, /system will be remounted suid so you won't have to go through this, and I think /system conversions don't end up in boot loops like /data and /dbdata.
Credits
Xcaliburinhand - without whom we'd all be on JJ4 and JI6. *shudder*
SztupY - Steam recovery is the shiz.
raspdeep, neldar, xan
I'll probably edit this a few more times as there will be things that I want to add but have slipped my mind for the moment.
Ok - I uploaded a copy of the Steam kernel here. It deserves its own thread and it will get one, just don't feel like doing it right now. Read through this post, realize there are some errors with filesystem conversion. Make sure you do backups, if you get into a boot loops, do a hard reset and reboot normally, you should be good. This is meant to be flashed via Neldar's SGS Kernel Flasher app, or something like Heimdall or Odin.
Alright...lets get started
Sent from my liberated Captivate via XDA App.
Just when I think I've finally found a ROM to stick with (Phoenix 1.0) after flashing just about every ROM I see on XDA.......along come some new candy!
yes!!!! definetely gonna donate thanks so much for the hard work mikey!!
Am I the only one that prefers the original clock/alarm that was on the phone? Select custom ringtone is nice and it seems easier than the car/home.
Sent from my SGH-I897 using XDA App
gdbusby said:
Am I the only one that prefers the original clock/alarm that was on the phone? Select custom ringtone is nice and it seems easier than the car/home.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
i love the original too. :/
Weeee!!! Finally!!!! Let see the awesomeness!!!
Running Assonance 5.0 - SpeedMod 256hz K12H - JL2
Mikey, does this contain the jpa wifi fix and external SD mount fix? Thanks.
Sent from my liberated Captivate via XDA App.
This post is no longer relevant. STOP LOOKING AT IT
I have two kernels in this, why do I have to keep hitting F5?
I guess my first post got deleted so I will do another one. This looks like it is going to be good.i actually enjoy the simplistic look.
Sent from my SGH-I897 using XDA App
Download's up.
Trying it out. Thank you.
Sent from my GT-I9000 using XDA App
and I was about to download your other rom.
madjsp said:
and I was about to download your other rom.
Click to expand...
Click to collapse
I was waiting for you to be about to download the other one so I could release this one.
just when i thought i would stop flashing today i see another rom come out.. life of a rom addict
Does this have the AOSP MMS App as well?
How is your Guy's battery life with this
Sent from my SAMSUNG-SGH-I897 using XDA App
What is a Steam Kernel?
This kernel uses SztupY's Steam Recovery instead of the standard ClockworkMod. Steam is based off of ClockworkMod, so all of the features you're looking for are here.
If it's based on ClockworkMod, then why would I want to install this?
Steam is a successor to the Universal Lagfix Kernel SztupY also made. Steam has a touchscreen interface at recovery, and a number of lagfix options, just like the ULFK, but with some additional options. Steam has options to convert /system to ext4 or jfs on top of the regular lagfix options. So, instead of using the buttons to locate that new ROM or theme or whatever, you just scroll down your screeen. Steam also has some advanced security features, which you can read about in SztupY's posts. One of the coolest things about Steam is that it automagically detects what filesystems you are using and re-writes init on the fly. So, if you're using an ext4 or jfs lagfix, you don't have to disable it before flashing Steam.
As you may have seen, there are two (I think minor) issues. For one, if you do it the way MikeyMike had people do it (use Voodoo to convert --> ext4), when Steam loads it will may mount /system nosuid, and it will seem like you've lost root. You haven't. It seems that either doing a /system conversion resolves this, so switch from /system formatted as ext4 to /system whatever, OR boot to Steam recovery, under 'boot options' select 'adb always on' and 'adb always root' or something like that, boot the phone, fire up adb and type
Code:
mount -o remount,suid /dev/block/stl9 /system
This will allow /system to be mounted with su access (kinda important!).
The other issue is that when you do a filesystem conversion on /dbdata or /data (one or both, I can't remember) after everything is done, you will get boot loops, doing a hard reset (hold down volume up/down/ and power)resolves this.
If you aren't doing filesystem conversions all the time, then this won't bother you much and these kernels are otherwise stable. This isn't a fault of Steam, SztupY designed it for 2.2, and we're using it on 2.2.1, a couple glitches would be anticipated, and these aren't anything that, imo, affect performance or stability.
As always - when doing these kinds of backups, make sure you have plenty of room on your SD card, or more than the total of the sizes of /data, /dbdata, /cache combined.
Finally, Steam NEEDS to be flashed either by Neldar's SGS Kernel Flashing App, or Heimdall (now for PC and OS X I think) or Odin via a tar file. I can't upload .tar files to xda, so I've attached a couple zips. These CANNOT BE FLASHED VIA CLOCKWORKMOD.
I've uploaded two kernels and a initramfs for anyone who wants to make a Steam kernel of their own. The OC/UV kernel is like my other ones, hopefully no issues with charging, voltage and clock speed can be controlled by xan's app, read other kernel thread for more info. The other kernel is basically a 'stock' reoriented kernel with Steam recovery.
Both kernels also have Neldar's 2.3 BacklightNotification Mod.
Some links about Steam
Here, and here.
Credits
Xcaliburinhand
SztupY
raspdeep
neldar
xan
So, if you think you're phone is getting 'charge death' (I prefer 'charger instability'...sounds a lot nicer doesn't it? ) try a couple things. (I don't think this is an issue with the Steam kernel here or with the most recent one from my other kernel thread, but if it is...)
- Get any kernel w/o the oc/uv patch.
- If you still want to try to find a oc/uv kernel which works for you, don't undervolt at all and tell me if it still happens with kernel #7 (12-23 build from my other thread). As far as I know, no one has had an issue with charger instability on that kernel. If it does still happen, I need to know the kernel version # and for good measure, the production code under your battery (can someone tell me what the name for this is again, I don't feel like shutting off my phone to check), it will be a number like 08.10, 10.10, etc.
- For it to be charge death, it has to occur while charging (I know, but you'd be surprised), it has to happen with a oc/uv kernel, you CANNOT have any setCPU 'screen off' profiles' (it's not just this kernel, screen off doesn't play nice on our phones afaik), and you cannot have any undervolt values set. (Read that closely - I'm not saying you can't UV, just that if it seems like charge death, remove all UV when charging and see if it happens. More below.)
- The reason I ask you to not undervolt at all and see if it happens is because I don't know if every other oc/uv kernel uses the stock factory voltages, so you may have been using UV settings that are referenced from an over-volted kernel, and so you might confuse freeze with charger instability.
- If even with the 12/23 build f kernels and not undervolting at all, you're still get shutdowns when charging, you probably want to get a different kernel. If you insist upon using that one anyway, try charging via USB instead of the wall outlet, it seemed to happen less frequently on older kernels, and I haven't had a charge death in weeks now, so, I'm good at least.
- See if your phone is one of the ones being recalled. If your phone is under recall and these don't work for you, I'm not sure what else I can do.
- These fixes work for me and a lot other people who had the same problem with other oc/uv kernels. Like I said, we're running these out of spec, so a few unlucky souls might not have phones that can handle this. Or maybe some of these kernels have been sprinkled with pixie dust and others haven't. If you find a different kernel that works for you by all means use it. It's all about choice people.
Thanks for posting this and for all your help in the other threads.
Sent from my liberated Captivate via XDA App.
Ok I am using the steam recovery in serendipity and you say doing it that way makes you seem like you have lost root. I haven't had any issues with my apps on my phone that require root but steam gives me a status 2 error when trying to flash themes...would doing a system conversion fix that or is that a totally different problem?
Sent from my SAMSUNG-SGH-I897 using XDA App
Anything different from the attached kernel in this thread and the one in Mikey's rom?
That could be it because you're probably trying to write to system with the update.zip. Check by running an adb shell (or fire up the terminal emulator app) and just type 'mount'. If you see something like
Code:
/dev/block/stl9 on /system type rfs (rw,[B]nosuid[/B],nodev,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8)
then yeah. Or like I said, use adb, but you might have to do that after every boot. Fileysystem conversion seems to be good.
Steam re-writes init on the fly, so if it's not doing the conversions at first, it apparently defaults to nosuid.
bts0uth said:
Anything different from the attached kernel in this thread and the one in Mikey's rom?
Click to expand...
Click to collapse
Ah well just updated to BLN 2.3, and added the no oc/uv one for people who don't want that.
This is what mine says when typing mount in terminal emulator...right or wrong?
/dev/block/stl9 on /system type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
Could we flash the no oc/uv over the stock kernel in serendipity without disabling voodoo?
Sent from my SAMSUNG-SGH-I897 using XDA App
Gurgs said:
This is what mine says when typing mount in terminal emulator...right or wrong?
/dev/block/stl9 on /system type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
Click to expand...
Click to collapse
If you don't see nosuid, don't worry about it. I had had Steam recovery on my phone all last week but I went from RFS --> jfs as soon as I flashed so I had no idea this was an issue before it was released. MikeyMike had the idea of putting on the ROM and people could try it out, which I thought was pretty good, and still is. Just wasn't quite as easy as we thought.
crupp said:
Could we flash the no oc/uv over the stock kernel in serendipity without disabling voodoo?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yes. BUT, since you aren't doing a /system conversion, what I wrote in the OP will probably apply to you.
Any progress on Voltage Control sticking?
MikeyMike01 said:
Any progress on Voltage Control sticking?
Click to expand...
Click to collapse
Any progress on making a ROM that doesn't have nine version in 48 hours?
glitterballs said:
Any progress on making a ROM that doesn't have nine version in 48 hours?
Click to expand...
Click to collapse
At least I fix what's wrong.
What is steam? This isnt a kernel we can simply flash with Odin?
MikeyMike01 said:
At least I fix what's wrong.
Click to expand...
Click to collapse
I'm flashing 1.9 now so we'll see about that.
psufan5 said:
What is steam? This isnt a kernel we can simply flash with Odin?
Click to expand...
Click to collapse
Steam is similar to cwm. It uses a pretty cool touch screen interface. Try sgs kernel flasher, its really easy to use. Don't forget to make a backup first.
Sent from my liberated Captivate via XDA App.
glitterballs said:
Any progress on making a ROM that doesn't have nine version in 48 hours?
Click to expand...
Click to collapse
You can, you just have to make a .tar of the zImage. You can't u/l .tar to XDA for whatever reason, so just posted zips.
MikeyMike01 said:
Any progress on Voltage Control sticking?
Click to expand...
Click to collapse
My voltages have been sticking since I downloaded your rom...i must of just got lucky or something...
Gurgs said:
My voltages have been sticking since I downloaded your rom...i must of just got lucky or something...
Click to expand...
Click to collapse
It sticks with the normal kernel, but not the steam one.
as requested by some users:
Flash with "one package/integrated package" with Odin;
ht tp://ww w. multiupload. co m/ NRKHF86ODJ
(remove spaces)
Please some more details
What is it exactly?
Criminal23 said:
Please some more details
What is it exactly?
Click to expand...
Click to collapse
its the same rom as http://forum.xda-developers.com/showthread.php?t=957123
but with /data and /cache converted to ext2 filesystem (lagfix).
/system was already /ext2 converted by Kyriilos
also note that this will wipe your /data partition, and do not wipe /data and /cache in recovery
Could you pls make it with the coming 2.2 Version, too
Criminal23 said:
Could you pls make it with the coming 2.2 Version, too
Click to expand...
Click to collapse
Yes, please. Make it for version 2.2 as well.
Kyriilos is the same person what Kyrillos
Improve theme
demistoja said:
Kyriilos is the same person what Kyrillos
Improve theme
Click to expand...
Click to collapse
its a misprint! My name is Kyrillos and not Kyriilos
Its done
Because Kyrillos post a version without lagfix, so we can implant apollos "app2sd fix"
[ROM] Kyrillos' ROM v2.2 Gingerbread Edition without lagfix
Lagfix + data2sd (Quadrant score 570 + Lot of space for apps)
EDIT: ITS REAL DONE!
Link
I have got a problem with Kyrillos's ROM 2.2 With Special Lagfix.
After flash every thing is great until I restore apps and reboot phone
system services crush (force close) all the time.
I flash it 4 times (directly form Kyrillos ROM 2.2 Normal and from original JPF),
every time i obtain the same result ;(
On Kyrillos ROM 2.2 Normal it's work like a dream.
Anyone have any idea why?
(i post here cuz i can't post in development yet)
How do you restore apps ?
No idea ... but lagfix is very experimental and the way it was done is not the best. Use lagfix to test : your phone may crash.
/system, /data and /cache are converted to ext2 fs : we didnt include any filecheck if the phone was shut down ... ext2 has no journal system and could make android instable in my opinion if the phone is shutdown (like if you remove battery).
Someone may correct me if I am wrong.
Y0RGI said:
I have got a problem with Kyrillos's ROM 2.2 With Special Lagfix.
After flash every thing is great until I restore apps and reboot phone
system services crush (force close) all the time.
I flash it 4 times (directly form Kyrillos ROM 2.2 Normal and from original JPF),
every time i obtain the same result ;(
On Kyrillos ROM 2.2 Normal it's work like a dream.
Anyone have any idea why?
(i post here cuz i can't post in development yet)
Click to expand...
Click to collapse
I restore apps by My Backup Root and it's always work.
Now I flash normal Kyrillos ROM 2.2 then install Motafoca lagfix and everything works well.
It's supposedly give the same effect but phone works without crushes.
Maybe it's a bug in that ROM or maybe my backuped stuff screw something up.
I really dunno
I installed Kyrillos' Rom 2.2 (Normal Version) yesterday. Really nice...everything is working fine so far. Does anyone know how to take screenshots with this rom? [Back + Home] doesn't work
DJ-Bouncy said:
Does anyone know how to take screenshots with this rom? [Back + Home] doesn't work
Click to expand...
Click to collapse
Try QtABD. It runs on PC and can take screenshots as well.
Edit: Sorry, you think probably of a standalone solution where you don't need a PC.
szabof1 said:
Try QtABD. It runs on PC and can take screenshots as well.
Edit: Sorry, you think probably of a standalone solution where you don't need a PC.
Click to expand...
Click to collapse
Yes, that's what I'm searching for. I thought taking screenshots by pressing Back+Home is a Froyo feature. But in this Rom it doesn't work. So if maybee I'll search the Market for a screencapture-app
Hi!
Can't write in dev part so to try here ... after all I am n00b
Installed 2.2 normal and then did lag+app2sd and everything is working nicely ...
I have a question though ... what if I decide to ay usd2.99 for LauncherPro Plus. Can I install it over the LauncherPro that is integrated into this ROM. I tried uninstall and install over but w/o success. It's system app (so it says) and I can't do aything about it. On previous e.g. normal JPF I was able touninstall reinstall LPPro. What did I miss?
Tnx.
LauncherPro Plus is essentially a key unlocking new features in free version, no need to install anything, especially reinstalling launcher.
To remove system app you have to root your phone (http://forum.xda-developers.com/showthread.php?t=778880) and get acces to system files (Root Explorer, qtadb, adb). Of course if you are removing one launcher, you have to have another already installed.
Nice hearing that apollo's lagfix is running well on kyrillo's 2.2, it's running nice on lestat's 1.1 as well.
Anyway to have all (Cahce\System\Data\ converted to ext2 and also partition the sdcard (apollo5801's lagfix). So in short, how can I have special lagfix + sdcard partitioned?
hi guys,
i think it would be wise to use the experience already earned from galaxy s i9000
from guys like supercurio, darky and hardcore, their work is VERY STABLE as it is heavily tested and proved to do miracles.
no one is using ext2 anymore,
i quote:
"Note: Only lagfixes using EXT4 are robust. Other lagfixes run the risk of data loss on freezing, hard-reboots, or sudden power loss."
they have opted for ext4 , to be more specific:
hardcore (http://forum.xda-developers.com/showthread.php?t=822756)
would recommend
DATA_FS=ext4
CACHE_FS=ext4nj
DBDATA_FS=ext4
and he has applied many other tweaks
i dont see why his experience cant be used for the galaxy 3
in addition the link below could be useful
[REF] Details about /system RFS corruption and HOWTO correct it (fix included)
http://forum.xda-developers.com/showthread.php?t=848471
Cheers