Database Users

[HOWTO] Speed Fix! (variant of mimocan fix)

This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated

Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!

I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?

The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks

Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).

andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.

_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack

Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?

spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...

_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?

andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)

I'm still a complete failure and now i get stuck at the galaxy s boot screen

Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?

after i put in
busybox cp -a /data/*
nothing happens it just sits there

igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data

but there is no trailing dot it just repeats what i typed and then leaves a blank space

same thing it just repeats it

igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.

WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!

Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App

[Kernel] - GB's Steam Kernel - OC/UV or Stock. Made from Unicorns and win.

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.

Super clean rom need advice

Guys I need you advice
I'm new with my fascinate.
With stock n default rom I try to upgrade my rom with some guide in this site. Here's what i'm doing :
For the first time
- root the phone
- cwm install (green)
- eb01 modem flash by odin
- super clean 2.2 non voodoo flash by cwm
all the first im doing is succeed nothing bad happen
Second
And then I just upgrade my cwm into the red. Its run well. And got froyo on my phone
Third
got the update 2.4 super clean non voodoo n try to flash it, is work too on my phone
The last I just want to change my 2.4nv into 2.4voodoo
Doing it with some guide on, flash it on cwm with voodoo lagfix disable before. N after rom flash finish I enable voodoo lagfix. Rom was running as well
The question always on my mind now after flash 2.4 voodoo version is should I have to flash EB01-voodoo kernel too or not??
thx

If you downloaded the voodoo 2.4, it came with the voodoo kernel. So you're all good. If you wanna make sure it's running good run quadrant from the market. If you get a high score your voodoo is working.
Sent from my SCH-I500 using XDA App

I just download the rom on this link http://www.mediafire.com/?29to6l4fkgaf5gg
From this link http://forum.xda-developers.com/showthread.php?t=910921
Flash in run
Before I run 2.4nv rom score is 900 on quadrant
N after flash voodoo version it's 1500 score
Do I have to flash eb01-voodoo kernel or not?

Nope.
Sent from my SCH-I500 using XDA App

L.O.L
think im doing the right way
Ok thx, but it's so strange for me, on non voodoo rom n quadrant score is so small but my phone notshowing any Lag/stuck/freeze. It just run fast. Same with the voodoo version
Could you tell me what is the defferent betwen non voodoo n voodoo version is?

Samsung's default filesystem is a ridiculous nasty kludge of FAT and some features from other filesystem types which allow it to work "well" with SSD/NAND storage called RFS.
A voodoo kernel includes support for the much more robust, faster, and more well-behaved-with-ssd ext4 filesystem.
Turning on voodoo the first time converts /system, /cache, and /data to ext4, which drastically increases filesystem performance over RFS.
In real-world scenarios, you'll notice the improvement in boot times and application loading primarily. Though some UI elements seem to perform better under voodoo, partially due to other fixes not related to the filesystem that are included.

AlexDeGruven said:
Samsung's default filesystem is a ridiculous nasty kludge of FAT and some features from other filesystem types which allow it to work "well" with SSD/NAND storage called RFS.
A voodoo kernel includes support for the much more robust, faster, and more well-behaved-with-ssd ext4 filesystem.
Turning on voodoo the first time converts /system, /cache, and /data to ext4, which drastically increases filesystem performance over RFS.
In real-world scenarios, you'll notice the improvement in boot times and application loading primarily. Though some UI elements seem to perform better under voodoo, partially due to other fixes not related to the filesystem that are included.
Click to expand...
Click to collapse
Thx for your info,
Think I will stay at voodoo version to feel it more with it

Noticed this with data2sd

Im using pzafroyo 2.2 that comes with data2sd. When I installed charge offline zip, it made the data2sd not work and when I rebooted it I had the rom back to fresh install. After recovering system everything went back to normal again, I dont get it. Isnt the image file in xrecovery folder all thats needed? it wasnt missing after the charge offline install. Also, even tho I was getting 2500+ benchmark w/data2sd I went ahead and ran it without it working and only got 1300 but the phone feels way faster and smoother, with data2sd (8gb class4) I was getting lags everywhere so its not worth it unless Im doing something wrong? I also noticed theres 2 charge offline files floating around, Im using the one labeled "proper fix", maybe that hindered the data2sd operation.

The offline charge fix should be implemented in all custom ROMs already so there was no reason to install it and that likely caused your problems. Data2SD isn't going to do anything but improve your quadrant score and cause lag especially with only a class 4 card.
Sent From My *Super Fly X10*
If I (or anyone for that matter!) help you, dont be afraid to press THANKS!

[TELUS T959D Fascinate]-Running S.U.R.F.A.C.E ICS

First of all I would like to give credit where credit is due and say thank you to SamHaLeKe for all the work he put into this port and all the other Developers involved to bring ICS to the SGS
If you would like a full run down of this ROM and what is included as any new developments, please visit the ROM thread
Now off to the good bits ...
Install
I AM NOT RESPONSIBLE IF SOMETHING GOES WRONG AND YOUR PHONE CEASES TO WORK. THIS IS NOT A DETAILED WALK THROUGH BY ANY MEANS. I AM ASSUMING YOU READ ONE OF THE MANY OTHER TELUS THREADS THAT HAVE THE FULL INSTRUCTIONS INCLUDED TO PERFORM THE BELOW STEPS.
Note: I am not going to post all the links to files as I do not have the time to update them everyday when something changes. I will however post links to the ROM and Kernel threads for your reference.
I decided to start fresh (and I mean fresh) from stock FROYO with a full SD format and the works.
Step 1
Flashed back to stock with ODIN. Again I used FROYO but I am sure GB would work. If you want to start fresh as I did, go to options storage and format the internal SD (13 GB).
Step 2
Download the ROM and Glitch V13 kernel (what I used) and copy them to the SD card of the phone. I suggest removing any external SD as not to copy the files to the wrong spot (guess what I did LOL).
Step 3
Flash voodoo kernel from ODIN to root and install clockwork recovery making sure that you do not repartition in ODIN
Step 4 - Note: The older voodoo kernel gave an "assert failed" error trying to flash the ROM through recovery)
Boot into recovery and wipe cache and dalvik then flash the Glitch V13 kernel from zip and reboot. At this point you will most likely be boot looping but no worries everything is OK
Step 4
Pull the battery and then boot into recovery with volume up + volume down +power. Wipe cache and dalvik and flash the ROM from the ZIP
Let the ROM boot and then again boot to recovery and flash the essentials zip.
Voila you should be running S.U.R.F.A.C.E ICS, aint it beautiful?
I continued and flashed add on packs 1 and 2 but that is up to you
Now for my findings thus far ...
I am in no way a power user when it comes to my phone but I do play with it a lot. I have to say that this ROM seems to be the one of the smoothest to date and seems to take to our device nicely.
Battery has been nothing short of great for me. Through the week I can easily get 2 days out of it (work all day). Now I also try to minimize the drain by turning off whatever I don't need like WIFI seeing as there is none where I work.
I flashed the JL3 modem and it seems to work good for me but then I don't live where you do so you may have better luck with another.
The kernel included in the ROM (if you read the ROM post) is Glitch V14 pre which runs amazing as usual although still in the development stage. This kernel has a lot of new features that I will let you read up on yourself here
The ROM also includes supercharger and thunderbolt scripts (I admit I have little to no experience with these but I do know they help).
No FC's with this ROM other then the video camera but I have seen some posts regarding this and have not got around to working on it but will be I am sure very soon. It looks like just a file update maybe but too soon to tell.
Live overclock seems to work if I leave the voltage settings alone but that could just be a lack of experience in this area but it never hurts to try. If anyone has settings that are working for them I would love to know what they are. I have set the live overclock to 120% or 1.2ghz and it runs fine again if I do not change the voltage.
It's only been about 3 days since the install but this is what I got so far. I would recommend giving it a try for sure.
I know there are a few of us on this ROM so post up your findings here.
Thank you
Buck

Similar but running Glitch v14
Thanks for the write up Buck. I have been running this rom (Surface) for a few days also but I came from cm7 to this one. I have also been toying around with it over the last few days which has gotten me in a few tight spots lol. I have my Volt control set to 1304, no voltage changes and it runs flawlessly. The modem I put on was the JVT which also seems to work well.
What I have learn about Live OC:
First you set your clock speed in Volt control, then flip over to NStools (that is the easy part)
IMPORTANT.... If you choose to mess with this, make sure settings in NStools is NOT set to apply on boot or make sure you have a good recovery to go back to. Found this out the hard way
Click on live oc and you can make changes here... If you read the articale from Glitch on this it will help alot (found in the OP for T959D).
Live oc clocks up the cpu AND bus so it affects the gpu and memory along with the cpu (very important).
Findings... some settings work fine, 105, 106,110, 114, 116. 115 seems to have issues and provides lower performance considerably lower.
I use AnTuTu to check how things are working. That being said, if you apply set at boot and you hit a setting that first craps out the phone, causes a reboot then your going to be in a bootloop or it will start reboot start reboot. This is why you DON'T do this or like I said earlier have a good recovery handy.
Right now I am only running 1304 and 100% and everything is fine except the prior mentioned FC on video cam. Oh I should mention also I am running the Lazy governor atm which also seems to work fine (default is on demand).
Anyways

Well I think we may have broken the record for the longest 2 posts on the first page in xda history lol. Happy flash year everyone
Sent from my GT-I9000 using XDA App

Didn't notice you guys mention this, but Glitch V14 has an option in CWM to clear NSTools settings. It's right above the option to clear voltage settings under the Glitch Menu.
It works well, believe me!!
-Maniac

I'm on ICS!
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.

baino said:
Thanks bucky!!
I'm on ICS now, with Glitch v14 but I have a few questions I'm hoping you can help with:
- The screen layout / icons seem shrunken to me? As well as the notification bar. General text and keyboards are fine. Is there a fix I can apply?
- With further versions from Surface can I just flash over top of what I'm on now or do I need to go back to stock?
- Do I need to use TI to bring all my apps back up (I get "App X has stopped working"), or is there a quicker way?
Thanks again.
Click to expand...
Click to collapse
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.

bucknetbucky said:
Well the shrunken icons are because of the DPI setting in the build.prop file. You can change it with a text editor (I use root explorer) to the default value of 240. It is listed as LCD Density.
To flash another version you should be fine to flash over what you have with a factory reset and wipe cache
Apps well I usually just re-download from the market. I have used TI and found I get the best result if I restore without data. Remember not all apps are compatible with ICS yet so that could cause issues as well.
Enjoy the ICS I know I do.
Click to expand...
Click to collapse
Hey Guys,
Why not just use rom toolbox? the build.prop tweaks give ya a niffty slider... no hackin involved...

Anyone got the files for stock GB?

cowvun said:
Anyone got the files for stock GB?
Click to expand...
Click to collapse
you looking for T959D?

Yes
Sent from my T959D on Darky's Rom 10.3.

Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?

baino said:
Rom toolbox worked for me, it's looking beauty now. Everything seems to be working well, except I get the occasional crash on dialer / contacts. Anyone else having the same?
I'm running LauncherPro, what are you guys running?
Click to expand...
Click to collapse
Nothing like that here maybe the way it was flashed I am not sure. Have you added anything?
Sent from my GT-I9000 using XDA App

Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.

baino said:
Only flashed the add-ons, and the launcher pack. Changed the LCD density and that's about it. I'm thinking it might be because I didn't wipe the sd card and start clean.
Click to expand...
Click to collapse
Depends what you did before flashing. I had issues after flashing a lot and never deleting anything lol
Sent from my GT-I9000 using XDA App

Working NSTools values for OC and UV
CPU:
Governor = Lazy
Min CPU = 100 (109 after live OC)
Max CPU = 1200 (1308 after live OC)
OC Value = 109%
Deep Idle = On
Custom Voltage
Arm:
1400 = unchanged
1304 = 1375
1200 = 1325
1000 = 1225
800 = 1150
400 = 975
200 = 875
100 = 875
Int Voltage
1400 = Unchanged
1304 = 1150
1200 = 1125
1000 = 1075
800 = 1050
400 = 1025
200 = 1025
100 = 925
Just set these values tonight and so far all is good and no crashes or reboots. See if it helps the battery as the days go by. Give it a shot or post your working values for others to try.
AND NO I NEVER SLEEP

bucknetbucky said:
Working NSTools values for OC and UV
Click to expand...
Click to collapse
Thanks for posting your OC and UV values. I'll give those a try.
I've been experiencing random crashes and reboots (woke up this morning to a dead phone). It was plugged in overnight but crashed at some point and did not charge. Battery voltage dropped down to almost nothing.
Anyone else experiencing random reboots?
I was using an OC value of 1304 (no live OC). UV values left stock. Ondemand governor, Deep idle ON, noop IO scheduler.
I did not format my sdcard prior to install. Just did a data wipe/factory reset, format cache and dalvik then installed according to the instructions. Installed Add-on Essentials and Add-on Pack One. All other apps were reinstalled from the market (after using market enabler and changing DPI back to 240 using ROM manager).
Everything works great except for the random crashes and reboots. I'll probably start from scratch again when v1.3 comes out (except I will format the SD card). Maybe even start from stock Froyo as recommended in the OP.
EDIT:
Tried the settings and my phone was not happy. It froze when setting the UV values. My phone seems to have a problem with any live OC value other than 100%. As soon as I increase it I lose all stability.

1.3 released and I am running it.
Sent from my GT-I9000 using XDA App

Settings
I'm on Glitch v14 pre5 and I just clocked it up to 1300 and added 104% live OC for a stable 1352, no undervolting battery sitting @ 68% 1 day 22hrs. I did turn off some stuff I dont use and had data running on and off for the whole time.
For the guys that are having problems with flashes, I generally wipe everything I know its a pain but I don't experience any problems either. I also wait until i have a full battery too. It seems to pay off in the long run...
Happy Flashing!!!

Phone and contacts are working well now, but I can't get app data to save. For example some apps t's&c's keep asking for approval everytime I open the app. Also beautiful widgets skins keep reverting back to default. I'm going to wipe, format the SD card and install 1.3 from stock Froyo. here's hoping.

bucknetbucky said:
1.3 released and I am running it.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just wiped and running 1.3 now. So far seems much better and faster than my last flash. You guys know of any way to change the haptic feedback intensity in ics?