Develop Bugs

[UTIL][DISCONT'D] CFLagFix 1.90 (ext2+ext3+resize+uninst support)

THIS TOOL HAS BEEN DISCONTINUED. IF YOU REALLY NEED A LAGFIX, USE VOODOO. HOWEVER, WITH LATEST ROMS I DONT PERSONALLY FEEL A LAGFIX IS STILL NEEDED, THUS I DON'T USE ONE, AND WILL NOT CONTINUE DEVELOPING ONE
About
Here it is, yet another LagFix tool. It's certainly not the first, but it does offer some things others do not (at the time of this writing).
This patch uses the ext2/ext3 image in /data method.
IMPORTANT NOTICE FOR FROYO USERS
(1) Use ext2. ext3 is NOT supported on Froyo, only Eclair
(2) The installation will fail if you apps installed to SD. Go to Settings -> Applications -> Manage -> On SD card. Click each app and click "Move to phone". In the end, the "On SD card" list should be empty. Reboot. Install CFLagFix. When the fix is installed, you can move apps back to the SD card if you wish.
Features
- Lots of checks to make sure the fix is possible
- This is not just based on a script, but a lot of commands are performed and their results rigorously checked to be what is expected
- You can select (from a set of presets) which folders you want to lagfix
- You can select how big the image should be (between 128mb and all the free space in /data minus 250mb, to prevent low storage space warnings)
- The actual moving of data from RFS to the image is done in a boot loop, while the files are not in use. This minimizes the chance of corruption during move (settings being lost, etc)
- Comes with e2fsprogs, and e2fsck is performed each boot to fix a corrupted image
- Comes with it's own busybox, so no need to install it, and no chance for conflicts
- If an ext2 image is used, it is tuned to not reserve any blocks
- If an ext3 image is used, it is tuned to not reserve any blocks and use journalling
- Also moves databases (safely)
- Uninstall option
- Resize option, resize your partition whenever you want, to whatever (possible) size you want
- "Full automatic" option, this will max out the image size while still preventing the low storage space warning, and will also reclaim the space from the backup folders and automatically resize the image to max again after that space is reclaimed. This generally results in an image of about 1.5 GB. It'll also leave some space in case the system still needs to write in /data but not in the image.
- Progress monitor ("educated guess" about progress, not exact, but pretty close, usually!)
A fair number of these seem to be unique at the time of this writing.
Notes
- e2fsck result is stored in /data/cflf/e2fsck_result.txt
- list of mounted directories is stored in /data/cflf/mountlist.txt
- if ext3 is used /data/cflf/imageisext3 file will be present
- my own test rom is JM2+root-with-update.zip+ClockworkMod
Known issues
- In case the image is heavily corrupted, e2fsck may take longer to fix it than the rest of the boot process. Theoretically this could result in data loss
- ext3 does not seem to be supported on Froyo ROMs JP1/JP2/JP3
Credits
- mimocan, ykk_five, RyanZA, and all others who have chipped in for various lagfixes
- cynogen, e2fsprogs built for ARM
- kalpik, busybox APK
- ofcourse the original authors of those tools as well
- myself, this is all based on ADB Magic code
Donations
Please feel free to donate: http://www.jongma.org/dx.php
Requirements
- Windows
- Microsoft .Net 3.5 framework
- Phone in USB debugging mode
- SuperUser
Before using ...
I strongly recommend using ClockWorkMod and making a backup of your ROM. Just in case Also, during any operation, I advise having your phone hooked up so I can draw power from the computer.
Usage
- Unzip the attached file somewhere
- Make sure your phone is connected in USB debugging mode
- Make sure you have SuperUser installed
- Run CFLagFix.exe
There are three tabs:
Install LagFix
This tab allows you to install the LagFix, and lets you configure some options.
I recommand leaving the "Full automatic" option turned on, if you do, just press "Install !" and everything will be arranged for you. If you turn this option off, you can configure some settings manually, but note that using this does not reclaim wasted space of the backup files.
Note that you can still select to use ext3 instead of ext2, even if in "Full automatic" mode.
When you press "Install !", the program will be finished quickly, but your phone may continue working for 30 minutes or so, and keep rebooting very often. If you have a lot of data installed, it may take even longer.
Do NOT even touch your phone until Android boots up again!
A lot of things are checked before the install will start. You will need about 50% free in /data for the operation to work, but it will check this before making any modifications on your phone.
Resize Partition
This tab allows you to change the current ext2/ext3 partition size. The slider will only let you select values that are actually possible, i.e., bigger than your current data usage and smaller than the total space that could be occupied by the image.
Clicking "Resize !" will reboot your phone and resize the partition. Again, this can take an awfully long time! Don't panic, just wait it out.
Uninstall LagFix
This will uninstall the LagFix. It will completely remove it. Before removing it, however, it will move all files out of the image and back into the normal filesystem again, so no data is lost.
Clicking "Uninstall !" will reboot your phone and perform the uninstallation. Again, this can take an awfully long time! Don't panic, just wait it out.
Note that uninstallation will only work if you are using less than 50% of the device's capacity, but again the program will check this before making any modifications on your phone.
You can only uninstall installations of CFLagFix 1.20 and newer !!
BETA
This is very beta, use at your own risk!
WARNING
This patch is NOT compatible with ANY other lagfix tools. Either undo those completely, or just don't use this. If you were using one of those, I'd personally recommend a complete reflash of the firmware before using this patch.
WARNING #2
Before trying 1.80, please see this post.
Download
<< 1.70: 632

Changelogs
1.80, 15-08-10
- Redone some crucial parts of the patching procedure (for all install, resize and uninstall). Should fix all remaining issues!
1.70, 13-08-10
- Added /data/app-private/ folder
- Added progress monitor (estimates.... not exact)
- Moved /dbdata/databases to it's own partition, much faster for smaller read/writes
1.60, 12-08-10
- Updated codebase to ADB Magic 0.9, fixes issues with some weird pre-existing installations of busybox
1.50, 12-08-10
- Added "full auto" mode, "one click" solution for beginners
- Added ext3 support
- Added resize support
- Added uninstall support
- Fixed some issues
- Update scripts
1.20, 11-08-10
- Everything has been moved to /data/cflf/ , this - amongst other things - fixes issues with JP3
1.01, 11-08-10
- Adusted a permission error which could cause the system to be unable to create any new databases
Fix for 1.00 users: there isn't any yet. This is *beep* to fix manually. I would advise this "unpatch" method posted here: http://forum.xda-developers.com/showpost.php?p=7616676&postcount=29, then repatch with the latest version.

CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."

lyno said:
CFLagFix.exe doesn't even run for me.
"The application failed to initialize properly (0xc0000135). Click OK to termiate the application."
Click to expand...
Click to collapse
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.

Chainfire said:
You sure you have MS .Net 3.5 framework installed ?
http://www.microsoft.com/downloads/...fd-ae52-4e35-b531-508d977d32a6&displaylang=en
The error message is a DLL initialization error... as CFLagFix doesn't explicitly use any DLLs, my guess would be the .Net framework.
Click to expand...
Click to collapse
Ah yes! I removed all .net frameworks on this works laptop to be able to install some old COM files. Will re-install and test.

This looks so awesome! Thank you!
Any chance for open sourcing this?

installing now
Well im gonna give this a shot, have just installed the african jg8 and rooted,am doing this fix now.
Then ill try the 1.2 overclock on top, ill post a score shortly .

Not bad though i see one problem... it's windows only ^^

select which folders you want to lagfix
Click to expand...
Click to collapse
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?

just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this? -> it doesn't recognize both my internal & external sd, but i can browse them properly in Estrongs/astro

veenone said:
After the process finished, the Android displayed information about damaged internal SD, but everything was working.?
Click to expand...
Click to collapse
That sounds scary, think I'll wait a while before trying!

RyanZA said:
This looks so awesome! Thank you!
Any chance for open sourcing this?
Click to expand...
Click to collapse
Not at the moment, but maybe in the future
Tayutama said:
Not bad though i see one problem... it's windows only ^^
Click to expand...
Click to collapse
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
danamoult said:
Sorry, bit of a noob here - what exactly do you mean by this? Why would we only want to 'lagfix' certain folders and not the whole thing?
Click to expand...
Click to collapse
You can't really lagfix all folders, as the process where the image is mounted is run asynchronously with the rest of the boot process. There will be havoc if the system can't load certain files because the image is not mounted yet. This is why you can't just lagfix the entire system, but only certain parts.
In the presets I have only added those folders that I feel are mostly safe to lagfix AND would actually benefit the speed of the phone.
Also, for some folders there is some discussion to whether or not it is beneficial to have them in the image, like /dbdata/databases. I personally feel it should be lagfixed, but not everyone agrees.
veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
Click to expand...
Click to collapse
I have not seen the "damaged internal SD" message before in any of my tests. It might be ROM specific (I'm personally using JM2). I would recommend rebooting (using the "hold power button + press power off" method) and see if the message still comes up. Let me know what happens.
And yes, feel free to post about it in your blog.

veenone said:
just tried out your tool on my stock DXJF4 (with apps in it, not clean condition). With default size as well (around 1200 mb)
Actually I used mimocan's fix before but everything was wiped by mistake and everything went to default condition.
After the process finished, the Android displayed information about damaged internal SD, but everything was working. Is that expectable?
Now I got 2260 using Quadrant, leap from 1700 with mimocan's fix.
Nice job Chainfire!!
Can't wait to use JM2 / DDJG4
btw, can I post this on my blog?
:update :
whenever I open gallery, it always says no sdcard detected... do you know how to fix this?
Click to expand...
Click to collapse
Replying to the same message again, hehe.
Now that I'm thinking about, how exactly did your device got wiped ? Anything less than an actual firmware flash does not completely remove mimocan's fix, AFAIK. To completely undo it you'd have to completely reflash (and get stock kernel back), and possibly remove the ext partition from your SD. In other words, if you "wiped" from recovery, this is not a removal of mimocan (AFAIK).
Gallery is working fine for me, by the way, and as stated above, I have not seen that message in my tests with JM2 (neither with a lot of apps installed nor a clean flash).
(Then again, this is the first release, so there might be issues )

Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.

well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!

Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
This fix is using exactly same space that is already reserved for user data and programs. And it is on the internal SD. So I really can't think how this fix could cause any damage at all. Thoughts?

I selected maximum Space, and now i have low internal memory. How to remove this fix or change the Space?

Daemos said:
Is it possible to do this onto an external SD card (provided one has one that is fast enough) so we do not risk any possible further damage to the internal card due to excessive IO.
I believe it would be quite difficult to replace the internal SD card, and in order to load custom roms (with update.zip) it must be mounted to the internal SD.
I'd much rather replace external SD cards if I had to choose between the internal and an external.
Click to expand...
Click to collapse
Use mimocan's fix if you want to use external SD - it is especially made for that! His thread is a sticky (at the top) in this forum.
veenone said:
well everything was restored to factory state when I went to CSC menu. I think mimocan's fix also removed since I got 800 in quadrant score.
Update: after I rebooted the sgs for a couple times, now it recognize both sd cards.. weird.. But that's fine since the issue is solved now!
Click to expand...
Click to collapse
Mimocan's fix uses Odin. Like update.zip's, a "factory reset" does not remove patches made in this way, only a real flash does.
Either way, happy to see your problem is solved

I think the problem was the system didn't mount sd cards properly after several boots from CFLagFix. So it needs more reboots to mount the sdcard with structure change properly...

Chainfire said:
Not at the moment, but maybe in the future
Can't be helped. Not going to release a non-Windows versions. Perhaps wine/mono will make it work, though I doubt it
Click to expand...
Click to collapse
It's a shame you can't open source this.
Personally, there is no way I'm going to run something like this without source - I believe you are just trying to help us out, but there is always the chance that you could be doing something damaging by mistake, or even installing a trojan on purpose.
I'll be following release though, looks awesome and hopefully you'll be able to open source this soon!

[UTIL][OUTDATED] One Click Lag Fix 2.0

[size=+2]This version is now deprecated in favor of the 2.0 APK version. Please see this link: http://forum.xda-developers.com/showthread.php?t=784691[/size]
This version is not recommended for use any longer.
Details about what this fix does:
Creates a VIRTUAL EXT2 filesystem inside the stock RFS filesystem on the internal SD card, with a 4KB block size. This means that this lag fix creates a buffer between the real filesystem and the android system. This buffer should reduce the amount of disk I/O required for all operations by utilizing EXT2 buffering, as well as not writing file access times to disk, etc.
Folders that are currently supported:
/data/data
/data/system
/data/dalvik-cache
/data/app
/data/app-private as a symlink to /data/app/app-private
/dbdata/databases is not supported. It appears to be ROM backed, and can cause problems if overwritten.
Benefits over version 1
1.5GB of application data available, with no data loss.
e2fsck of the EXT2 partition on each boot.
Correct busybox version included! YES!
/app and /app-private directory included in the fix for faster application installs.
/dbdata/databases included in the fix, expected to give a big performance boost for apps that use it.
Mounts instead of symlinks for extra performance as OS does less work (about 100 or so more quadrant).
Benefits over other lag fixes
Open source, with full comments and ease of editing.
Works on any and all firmware versions, including any yet unreleased froyo versions (that don't change file structure).
Credits
Big thanks to mimocan for putting us all on the right track in how to sort out lag problems!
Big thanks to ykk_five for showing us all how well loopback filesystem mounting works!
Big thanks to cyanogen mod for e2fsck
Requirements for One Click Lag Fix 2.0
Rooted phone - http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
Windows computer with SGS Drivers (Samsung Kies), or the ability to read through the batch file and run it yourself.
(Beta Release) The ability to reflash your device if something goes wrong.
No other lag fix installed. If you installed One Click Lag Fix 1.0, then use the uninstall function which came with that lag fix before running this lag fix. (Untested but assumed to be working, please help out here.)
1.5GB of freespace on Internal SD Card for swap files while the fix is working (/sdcard).
"Internal phone storage" in Settings->SD Card must read greater than 500mb (0.5GB) of free space.
How to run One Click Lag Fix 2.0
Place your phone into USB debugging mode: Settings->Applications->Development
Attach your device to your computer. Do not mount the drives.
Download the attached ZIP file.
Unzip to a folder of your choice.
Double click "lagfixme.bat".
Don't double click "unlagfixme.bat".
Wait for it to complete.
You will need your phone to be unlocked when it runs the script, so that you can accept the permissions request that will appear on your device.
How to remove One Click Lag Fix 2.0
Double click "unlagfixme.bat"
Wait for it to complete.
Known Issues For All Versions
Some custom firmwares use up all available space in /system. This fix requires some libraries to be placed in /system/lib. These libraries are used to create the filesystem properly, and to check it for errors on every boot.
If your firmware does not have the available space (around 1mb) in /system, do not use this fix! Your phone will not boot and will have to be restored from backup / reflashed.
Current known firmwares with this issue: None yet. Please provide the firmware version+mods if you encounter this issue. It will show up as an out of space error in the log, under 'Copying libraries'.
Known Issues 2-1, 2-2
Paid apps from the market have issues.
Google maps and other pre-installed ROM-backed applications have issues.
2-3 Changes from 2-2
/dbdata has been removed. This fixes maps issues.
/app-private is now a symlink to /app/app-private. This fixes paid apps issues.
Alternate installation methods for similar fixes
Tayutama has made an update.zip version that is easy to install - http://forum.xda-developers.com/showpost.php?p=7632258&postcount=208
Chainfire has a .NET version of this fix with some nice features - http://forum.xda-developers.com/showthread.php?t=751513

Frequently Asked Questions
Q: My apps are force closing while this fix is running, and I can't use my phone!
A: By design. The script has backed up/copied your apps over to the internal SD card (remember the requirement about 1.5GB of free space on the SD card?). It is now overwriting them with a 1.5GB file. As the file overwrites an app that is trying to do something, it will probably force close. This is normal.
Closing all running apps, and removing widgets before running this fix can make the process much smoother, though.
Q: The script can't transfer files to my phone / The script can't run / Help help I'm dieing!
A: Read the first post again.
Q: My paid apps from the market don't show up.
A: I will hopefully have a fix for this sooner or later. Hold tight! It's in the known issues. I don't have access to paid apps, so I can't test this.
Q: Does this need busybox?
A: No, busybox is included.
Q: I only have 200mb of free space now! What gives?
A: The lag fix has made a 1.5GB file, and is storing all of the data inside there. The side effect is that the free space meter is now incorrect. Sorry, this can't be helped.
You can check real free space by using ADB like this:
Code:
adb shell
su
busybox df -h
Q: When I use a backup tool, the backup is now 1.5GB big! It's taking forever!
A: The backup tool isn't designed to work with this fix. It will work, it just won't work well. Hopefully this fix will be short lived, and either Samsung will give us a new update, or someone will give us a good custom firmware that can natively mount what we need, where we need it. Or someone might come out with a better backup manager. Until then, we suffer.
Q: Will a reflash wipe this fix?
A: Yes, a reflash will wipe everything this fix did.
Q: Can this brick my phone?
A: If you know how to get to the download mode from power off (hint: volumedown+home+power), then almost nothing short of throwing your phone off a tall building can actually brick it. If you can't do this though, or don't know someone who can, then you're better off waiting for samsung to release a fix. Anything that moves files around on your device has the potential to break things, and this fix has no QA department.
Q: Why is /dbdata not included in your fix, but other people have included it?
A: Other people have included it in the same way my 2-2 fix includes it. However, /dbdata is ROM backed. This means that the real files are on ROM, and only the changes appear in the /dbdata folder. When copying or moving files from this folder, you would need to specify each folder by exact name to ensure that it was copied across, and each firmware can have their own names. (This is because RFS wildcard will not catch an unused ROM backed file.) In some cases, you can get lucky and have this work perfectly because you have already used all the files in /dbdata. There is no fail safe method to do this though, and /dbdata does not make a big difference to performance. (It is already on NAND flash.) If you want to try your luck, v2-2 is still available.
Q: Why does this lag fix work? Is it slowly destroying my phone?
A: Let's say an application counts from 1 to 10, and writes the value each time to disk.
Stock:
1 -> App tells RFS to write 1 to disk -> RFS writes 1 to disk -> RFS writes journal saying to changed the value on the disk.
2 -> App tells RFS to write 2 to disk -> RFS writes 2 to disk -> RFS writes journal saying to changed the value on the disk.
..
9 -> App tells RFS to write 9 to disk -> RFS writes 9 to disk -> RFS writes journal saying to changed the value on the disk.
10 -> App tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 20. Speed: SLOW! Wear and tear on disk: HIGH!
Lag Fix:
1 -> App tells EXT2 to write 1 to disk -> EXT2 stores 1 in RAM.
2 -> App tells EXT2 to write 2 to disk -> EXT2 stores 2 in RAM.
..
9 -> App tells EXT2 to write 9 to disk -> EXT2 stores 9 in RAM.
10 -> App tells EXT2 to write 10 to disk -> EXT2 stores 10 in RAM.
..
EXT2 tells RFS to write 10 to disk -> RFS writes 10 to disk -> RFS writes journal saying it changed the value on the disk.
Total physical disk writes: 2. Speed: FAST! Wear and tear on disk: LOW!
This isn't exactly what is happening, but it gives you the general idea.
Q: Can this mod work on other Android devices? Would we see a performance boost on them as well? If not why is it limited to the Galaxy S?
A: SGS has very very good hardware, but it has some parts of it's hardware poorly implemented. The filesystem that samsung chose to use is custom-built using FAT32 as a base, RFS. It has a lot of the problems that FAT32 has, and should have been left back in the 90s, or even the 80s.
One of the big issues with it is how it handles multiple requests - it blocks. It blocks everything. When your mail app wants to read the mail you just tried to view, but your twitter app is busy writing a new tweat it just received, your mail app is forced to wait.
This is bad, but it could be worse! And it is... your twitter app didn't just get one tweat, it got 50 tweaks. It is busy writing the tweats one by one to the filesystem. This would be fine, since all modern filesystems will buffer writes, so instead of writing each one at a time, they will batch them together and write it as a big chunk. Uh oh - RFS does no buffering at all! After each write, it will also write an update to the grafted-on journal system. Guess what happened to your mail you were trying to view while all this happened? It 'lagged' and you got a black screen for half a second, before the mail popped into view.
Luckily the hardware on the device is so good that you usually don't even notice the problem until you have a lot of apps running, all writing their updates when you unlock the phone.
This is mostly speculation based on experiments done on RFS -- RFS is closed source, and we have no idea if the problems are just badly set settings (such as a block size that is too small), coding bugs in the implementation, or if RFS is just really that badly designed.
This fix just grafts a buffer on top of the RFS filesystem, using a very very simple and fast filesystem, EXT2. It fixes most of the issues by writing to RFS as seldom as possible.
So no, this fix won't fix other devices, since they're already running quite close to maximum speed. The SGS at stock is running nowhere near maximum speed, and this lag fix takes it a bit closer. You could probably speed up other devices by tweaking the filesystem settings to give them a big buffer or similar, but it isn't really needed. (I haven't actually tried to put an EXT2 onto any other Android phone, as I don't have any other Android phone, so this is just speculation.)
Q: My phone is fast now!
A: Yeah.

Oh, awesome. I managed to post this in the wrong forum. Doh!
Could a moderator please move this to Android Dev sub forum?

haha looks awesome dude but you are correct, wrong section im gonna try it now, will report in 5 mins!

A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is

abra-cadabra...
*POOF*
Done!

E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.

sirphunkee said:
abra-cadabra...
*POOF*
Done!
Click to expand...
Click to collapse
Thanks.

RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
E_man5112 said:
A few people in the other thread said they had the first lag fix working on the captivate. Anything that might change that with this release? I came to download the old one, and here a new one is
Click to expand...
Click to collapse
I'm running the manual ext2 fix with Q scores 2000+. I'll try 2.0 Util tonight and post feedback....

Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk

gonna test report in 5minutes

RyanZA said:
The old one is still here. Nothing has changed that should stop it working on the captivate though, but it is completely untested. Use the 1.0 (which has had a lot of testing) until this one has been put through the paces.
Click to expand...
Click to collapse
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!

About what lag is this?
Sent from my HTC Desire using XDA App

Dominik06 said:
Someone got some benchmarks?
Maybe for xxjp3? I only reach 1900 in quadrant.. /:
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Benchmarks are roughly the same as 1.0. You can expect about 100 points more on average though, at least on my phone.

I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?

Zilch25 said:
I'm in the process of flashing back to stock on my Captivate so I can give this a legit test. I'll report back here and let you know how it goes. Assuming my Captivate doesn't melt I'll update my OP from the thread about the original fix in the Captivate section!
Click to expand...
Click to collapse
Just as long as you point out that this fix isn't heavily tested yet!

RyanZA said:
Just as long as you point out that this fix isn't heavily tested yet!
Click to expand...
Click to collapse
Oh I know, I'm going to emphasize that heavily, lord knows I don't want to get stuck on tech support all night

clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Thoughts? That's bad.
You should be seeing roughly 215mb free. Did you see any errors in the log at all?

Everything is working fine for me. First reboot after lagfix had some problems with downloading apps from market, but after a second reboot it got fixed.
"Biggest" problem now, is just the phone stating that my internal phone storage is too low, with an icon on notification bar that I cannot remove. Already deleted some .bak from /data folder, any more tips what I can delete to get rid from this message?
Regarding the fix. apps are indeed much more snappier, no lag on the system when installing apps from market, and overall if the phone would continue like this for the next 48 hours, lag fix form me is solved. I had some problems after some 24h, with some lag, even with the previous version of the lag fix.

clubtech said:
I just removed the V1 version and finished the V2.
It finally finished and rebooted the phone. now it tells me my internal memory storage is full. None of my Widgets will load.
Looking i see only 14MB free in internal storage.
thoughts?
Click to expand...
Click to collapse
Looking through my old V1 remove script, I believe I was leaving behind the .bak files! Nastyyy... I'll update V2 to remove those if they're there on install. Will hopefully clear up any problems.

[Q] missing space in /data partition

I have a really strange behavior on my data partition:
df show that the partition is almost full (1294 Mb used in a 1299 Mb partition). I got a low space warning this morning, that's how I noticed it, but I am not sure since when exactly I have so much in /data.
Now the strange thing is that I do not have so much apps installed, and indeed, using adb shell, a "du -a -d1 /data" report about 307 Mb used (157 Mb in /data/app, 83 Mbin /data/dalvik-cache, 60 Mb in /data/data). This is perfectly in line with what application manager tell me on my phone, if I quickly sum the reported spaces of the different apps installed.
I do not see any big file in the partiton (anyway, du -a should have counted files directly in data, not only directories), not even hidden files (starting with a ".", for those not familiar with unix conventions).
So now I wonder, where is this Gb of space gone? I should have at least 900 Mb free, but have 4 Mb (and this is after I removed an unused app, just after the low space warning I had 20 Kb free only!)
I suspect a rogue app doing something stupid (like keeping a very large log) or nasty (some malware), probably in the last ones I have installed....but how can it use memory without it showing somewhere (even with direct tools like "du")???
BTW, my last apps are, in reverse order of installation, blueputdroid, StabilityTest, CPU Spy, Barcode scanner,....
CPUSpy is a possible candidate for keeping a large log, but it is a quite well know app, so I somehow doubt it is the culprit...
Anybody had a similar problem, of some new ideas how to solve this? a tool that can check what use all this space on /data?
I am on CM7, nightly 110817-1717-BOOT179. I just finsihed a titanium backup of my apps, and my next step (once my battery is charged) is to reinstall CM7 after a data wipe (I am a little bit reluctant about it, cause I will have to reinstall all apps and swype.
[update]
Before cleaning data and doing a full reinstall of CM7, I did a simple reboot and tadaa, problem gone: df shows the same 340 Mb in /data partition as du gave, so missing space is back. Looks like a possible CM7 problem, I will report in CM7 thread...This is a little bit worying though, I fear fs corruption of my internal memory...
Thanks for any infos/solution about this,
cheers,
Greg.

*SOLVED*[Market crashing constantly]-The app Market(process com.android.vending)

I just installed cyanogen mod 7.2 stable(It's a clean install and i have wiped every thing) following that installed the latest gapps package(gapps-gb-20110828-signed).
The market would not even load and crash constantly.
I have tried these tips:
1.Cleared data and cache (settings-> applications-> market -> Then clearing cache)
2.Wiped Dalvik cache
3.Fixed permissions.
4.Changed "language"
5.Re-installed gapps package.
All this was to no avail.
Downloaded "jelly bean" market and installed it.
Now the market would load ok but it crashes when i try to download some application.It sucks.
Any suggestion ?

Try Increase your MTD Partition if you have any... It should fix it... If not, delete your account from the settings (Accounts) and log on while opening PlayStore. Hope it helps.

Have you flashed the right Gapps? Some of the latest ones are for ICS Users and i have found they dont work.
Just google "Gapps" and then find the one without ICS
Hope this helps

MacGyver Jack said:
Have you flashed the right Gapps? Some of the latest ones are for ICS Users and i have found they dont work.
Just google "Gapps" and then find the one without ICS
Hope this helps
Click to expand...
Click to collapse
Not working....yes,I am flashing the right gapps zip.
http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
I have also verified the MD5 checksum.

olu.danNY said:
Try Increase your MTD Partition if you have any... It should fix it... If not, delete your account from the settings (Accounts) and log on while opening PlayStore. Hope it helps.
Click to expand...
Click to collapse
Deleting the account and factory reset is not working....even installing the CM 7.2 again and again is not working.
What does it have to do with MTD partition ?I have got sufficient internal memoery as i told you that it's a clean install and I don't have any app installed on my device except custom CM apps.

What about going to Setting > Manage applications > Market > Force close
I know you may have tried it and seems silly but i had a problem updating my apps and i did this and everything seems to work. What about a reboot?
Edit: I found this temporary workaround so see if this helps!
Here is what I did:
1- go to app manager from settings,
2- uninstall the latest version of google play store
3- clear data and cache of google play store
4- install version Google Play Store v3.5.19
5- when you open the market, google will still prompt you to update to the latest version (dont continue, leave it as it is)
6- if you want to update/install the apps do it thru the browser in your phone/computer (it will straight away update in your phone)

optimusodd said:
Deleting the account and factory reset is not working....even installing the CM 7.2 again and again is not working.
What does it have to do with MTD partition ?I have got sufficient internal memoery as i told you that it's a clean install and I don't have any app installed on my device except custom CM apps.
Click to expand...
Click to collapse
If you have Custom MTD partition, the issue may be, you have a low space reserved for System (Where GAPPS are installed) and more for Data.
Try using 175, 15... It is sufficent enough to run smoothly.
Cheers.

olu.danNY said:
If you have Custom MTD partition, the issue may be, you have a low space reserved for System (Where GAPPS are installed) and more for Data.
Try using 175, 15... It is sufficent enough to run smoothly.
Cheers.
Click to expand...
Click to collapse
Ah hell,why the hell didn't I ever think of this ?
Thanks for the life saving tip ,still not sure though if it was market version related or the system partition related.
Increased the partitons to [mtd 175 15].Market took a while,got updated to version 3.7.13 and it's working now.Really appreciate your help.
BTW,How did you figure out that [mtd 175 15] will work on "CM 7.2 Stable"?Just wondering can’t we take some more space from “system”.I have had [mtd 140 5] working well with "CM Nightly”.
Not sure how much we can take from system to flash CM 7.2 Stable but I guess we can still reduce "cache" to 5MB.
http://forum.xda-developers.com/showthread.php?t=1233340
What do you think ?

optimusodd said:
Ah hell,why the hell didn't I ever think of this ?
Thanks for the life saving tip ,still not sure though if it was market version related or the system partition related.
Increased the partitons to [mtd 175 15].Market took a while,got updated to version 3.7.13 and it's working now.Really appreciate your help.
BTW,How did you figure out that [mtd 175 15] will work on "CM 7.2 Stable"?Just wondering can’t we take some more space from “system”.I have had [mtd 140 5] working well with "CM Nightly”.
Not sure how much we can take from system to flash CM 7.2 Stable but I guess we can still reduce "cache" to 5MB.
http://forum.xda-developers.com/showthread.php?t=1233340
What do you think ?
Click to expand...
Click to collapse
I use mtd 140 20. Reducing the cache to 10 caused the force closing of market for me.

saadislam said:
I use mtd 140 20. Reducing the cache to 10 caused the force closing of market for me.
Click to expand...
Click to collapse
Are you sure you are running "CM 7.2 Stable" on HTC Buzz(Wildfire).
I tried [mtd 140 5] and it was causing "The application Market (process com.android.vending) has stopped unexpectedly. (FORCE CLOSE)".

optimusodd said:
Are you sure you are running "CM 7.2 Stable" on HTC Buzz(Wildfire).
I tried [mtd 140 5] and it was causing "The application Market (process com.android.vending) has stopped unexpectedly. (FORCE CLOSE)".
Click to expand...
Click to collapse
Try [mtd 140 20] . Like I said before reducing cache gave me force close. This configuration works fine for me. I was using cm7.2 stable since its release but now I am using lewa with the same partitions.
Sent from my HTC Wildfire using XDA

Don't ever, EVER underestimate olu.danNY's advice!
And search a lil' before posting... I've had the same problem not so long ago:
http://forum.xda-developers.com/showthread.php?t=1689239

I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.

olu.danNY said:
I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.
Click to expand...
Click to collapse
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS

slymobi said:
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS
Click to expand...
Click to collapse
Sorry... I guess that ain't clear enough... What I meant is this... Remove some stuffs from the ROM and Increase your Custom MTD partition... For example, if 100, 10 makes it run smoothly without edit, after edit, 90, 10 might run it good giving you extra 10MB for data... Hope I am clear here.
Cheers.
Sorry for double posting... Connection ish...
---------- Post added at 10:39 AM ---------- Previous post was at 10:27 AM ----------
slymobi said:
I kind of agree with most of your post,I only ever use ext for sense roms.
You say " Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need" I now what you mean but this doesn't increase your partition size,removing files etc from system only frees up space in the partition not increase it. Custom mtd is the only method I know to increase system partition. Regards slym.
MokeeOS
Click to expand...
Click to collapse
Sorry... I guess that ain't clear enough... What I meant is this... Remove some stuffs from the ROM and Increase your Custom MTD partition... For example, if 100, 10 makes it run smoothly without edit, after edit, 90, 10 might run it good giving you extra 10MB for data... Hope I am clear here.
Cheers.

HipHopBlond said:
Don't ever, EVER underestimate olu.danNY's advice!
And search a lil' before posting... I've had the same problem not so long ago:
http://forum.xda-developers.com/showthread.php?t=1689239
Click to expand...
Click to collapse
TBH I had done enough research to fix the issue.I did what one usually would have considered good research else it shouldn't have taken more than 5 endless days and nights
Even on CM forums,Android forums and several blogs.Don't know why couldn't find your post.
Anyway,"olu.danNY's" advice helped me else i was going to ditch CM7 for some other ROM .In my opinoin there should be a thread where users can update their working MTD partitions regarding their ROMs.
Right now I am running CM 7.2 Stable with [mtd 140 15] and some other users are running it even with [mtd 130 15]. i.e cache partiton was the root of the trouble.

olu.danNY said:
I found out the partition size because I also wanted more space for Data as I don't like installing apps on SD (It can easily get corrupted as you use the SD with your PC during File Transfer, etc and or malfunction as some SD cards aren't that strong and I don't trust any!). That partition made it run.
Another way you can increase your partion size is simply by taking out pre-installed apps and or ringtones/notifications, etc you feel you don't need (My style). Anyway, I run Erwin P's ICS on Wildy now while having a backup of my CM7 incase I need to use the Camera/Video app again... LOL (I haven't tried using the dual booting thing... Always speculating, say I am lazy... Will try that out someday soon).
Anyways... Glad you have your phone working now.
Cheers.
Click to expand...
Click to collapse
I also prefer removing pre-installed apps using TB but that doesn't really help you that much.
Custom MTD partition does the real rescue and you can also use "S2E" to gain more space by moving apps to Ext partition e.g games,maps.Just make sure you don't move app data to Ext.

SOLVED
P.S. Don't attempt to shrink the cache partition "too much".
Keep it(Cache) ≥ 15

optimusodd said:
SOLVED
P.S. Don't attempt to shrink the cache partition "too much".
Keep it(Cache) ≥ 15
Click to expand...
Click to collapse
YMMV - especially with CM7. It has been mentioned a few times over the forum that CM7 has a bind script which makes your whole /data partition used as cache - as long as it's activated (default) and not corrupted there shouldn't be any problems with the play store. No idea regarding other situations but I know of people running a 5MB cache partition on CM7...

eventcom said:
YMMV - especially with CM7. It has been mentioned a few times over the forum that CM7 has a bind script which makes your whole /data partition used as cache - as long as it's activated (default) and not corrupted there shouldn't be any problems with the play store. No idea regarding other situations but I know of people running a 5MB cache partition on CM7...
Click to expand...
Click to collapse
Yep,I know CM7 has some sort of script that automatically moves cache to data partition if it overflows(larger than the cache size).
I have had [mtd 140 5] working well with "CM Nightly”.
No idea why it is causing trouble with CM7.2-Stable. Maybe it's lacking that script which makes it sufficent enough to run smoothly if cahce partition is <15.

[Q] Mildwild 4.3 (Oxygen) bind sd-ex

Hello Folks,
I have just moved from MW CM 5.0 to MW 4.3 (Oxygen) due to some call-delay issue of the first one.
MW 4.3 is quick and with no major bugs. the only bad surprise is the memory availability. Making a Titanium restore of all the previouse app+dada I crashed in the annoying "not enough memory" message.
I imagine that the fact that the M2SD is managed internally change the performance of it (true?). By the way I was playing with the different option trying to gain some space and I came across a new functionality (new for me) such as "bind /data/data to sd-ext/app-data" not really sure what it does but it increased my free internal memory from 12mb to 89mb. GREAT !! the only problem is that the overall speed of the system went drastically down. I guess it s normal as application will read their data from the SD instead of the quicker internal memory. Unfortunately with this option on the whole gsm was not usable anymore.
My question is: Is there any way to free more memory using this ROM? (with a decent GSM's response time)
Thanks for your help
Stefano

stegal said:
Hello Folks,
I have just moved from MW CM 5.0 to MW 4.3 (Oxygen) due to some call-delay issue of the first one.
MW 4.3 is quick and with no major bugs. the only bad surprise is the memory availability. Making a Titanium restore of all the previouse app+dada I crashed in the annoying "not enough memory" message.
I imagine that the fact that the M2SD is managed internally change the performance of it (true?). By the way I was playing with the different option trying to gain some space and I came across a new functionality (new for me) such as "bind /data/data to sd-ext/app-data" not really sure what it does but it increased my free internal memory from 12mb to 89mb. GREAT !! the only problem is that the overall speed of the system went drastically down. I guess it s normal as application will read their data from the SD instead of the quicker internal memory. Unfortunately with this option on the whole gsm was not usable anymore.
My question is: Is there any way to free more memory using this ROM? (with a decent GSM's response time)
Thanks for your help
Stefano
Click to expand...
Click to collapse
Well... that's the only option available on that rom, is to enable and mount sdext, that way it will move apps to the sdcard. I don't think it moves dalvik. Either way, what's your sdcard and class? Usually moving only apps doesn't really slow nothing important unless it's a class 2 card or some card with slower speeds. Even moving dalvik the rom should stay fast IMO. There's a slowdown but not that much.

MidnightDevil said:
Well... that's the only option available on that rom, is to enable and mount sdext, that way it will move apps to the sdcard. I don't think it moves dalvik. Either way, what's your sdcard and class? Usually moving only apps doesn't really slow nothing important unless it's a class 2 card or some card with slower speeds. Even moving dalvik the rom should stay fast IMO. There's a slowdown but not that much.
Click to expand...
Click to collapse
I think that option I used "bind" move app and data to sd-ext. my sd is a class 4.

stegal said:
I think that option I used "bind" move app and data to sd-ext. my sd is a class 4.
Click to expand...
Click to collapse
if u check the attachments for the rom in the development thread, there should be a dalvik2sd.zip there, i think i posted it there ages ago. just flash it in recovery.
Sent from my HTC Desire

dalvik2sd
jmcclue said:
if u check the attachments for the rom in the development thread, there should be a dalvik2sd.zip there, i think i posted it there ages ago. just flash it in recovery.
Sent from my HTC Desire
Click to expand...
Click to collapse
Jm,
I have a comment for you. First while I was looking for you post (could not find it though) I came across something that goes against your post, please read the following
<<
Do a clean installing!
Tips:
To enable Apps2Sdext and/or Data2SdExt visit Settings|Applications|Development.
To set the default installation partition go to Settings|Applications.
To move applications from sd-ext|sdcard|internal Settings|Applications|Manage Applications.
There is no Dalvik2SdExt because .dex will follow the location of the apk, so if you install an application on sd-ext the dex will be on sd-ext, the same applys for internal or sdcard.
Do not use A2sd scripts. >>
So where is the truth. Do I need this script or not. If you can explain me why could you also provide a link to this script?
Thanks in advance
Stefano

il post it later if u want it, im on my phone. u will get more memory
Sent from my HTC Desire

jmcclue said:
il post it later if u want it, im on my phone. u will get more memory
Sent from my HTC Desire
Click to expand...
Click to collapse
The part that confuse me is that "There is no Dalvik2SdExt because .dex will follow the location of the apk, so if you install an application on sd-ext the dex will be on sd-ext, the same applys for internal or sdcard."
I do not understand .. what he is saying, there is not dalvik2Sd and there is not need to have one (something like the A2SD) or there is not dalvik2sd so go ahead to install one.
if you know that the dalvik2sd script can free some space without side effects...pls post it
thanks

stegal said:
The part that confuse me is that "There is no Dalvik2SdExt because .dex will follow the location of the apk, so if you install an application on sd-ext the dex will be on sd-ext, the same applys for internal or sdcard."
I do not understand .. what he is saying, there is not dalvik2Sd and there is not need to have one (something like the A2SD) or there is not dalvik2sd so go ahead to install one.
if you know that the dalvik2sd script can free some space without side effects...pls post it
thanks
Click to expand...
Click to collapse
basically if u check the box to install apps in sd-ext, from "now" on apps will install on sd-ext, but there is aready dalvik cache on ur phone before u check the boxes and thats what the dalvik2sd.zip moves(i think). iv used the zip and has no effect on performance or anything, it just free's up a wee bit of space.
il post the zip in bout 2 hours coz im busy. if u look at the OxyZM thread, click the attachments, the file is there.
Sent from my HTC Desire

jmcclue said:
il post it later if u want it, im on my phone. u will get more memory
Sent from my HTC Desire
Click to expand...
Click to collapse
hi Jmcclue,
I tried to find your post...without result. I found one where you say that it was possible to download "click the wee paper clip", ok now I sound really silly but...where should I click? (no..I am not a blondie even if I sound like it )
F1, F1!!
Stefano

stegal said:
hi Jmcclue,
I tried to find your post...without result. I found one where you say that it was possible to download "click the wee paper clip", ok now I sound really silly but...where should I click? (no..I am not a blondie even if I sound like it )
F1, F1!!
Stefano
Click to expand...
Click to collapse
lol il just upload it
Sent from my HTC Desire

Dalvik to sd for MildWild Oxygen and where the "wee paper clip" is lol (attachments).
md5 - d7ba5d384a78d14e57d293cd877eef7b

jmcclue said:
lol il just upload it
Sent from my HTC Desire
Click to expand...
Click to collapse
...hello jm just coming back to thank you for your support. Finally I have a stable situation. Nevertheless after installing the script you have uploaded nothing changed. I had to factory reset, reinstal CM 4.3, install your script and everthing went smooth. Now it s 2 weeking I am keeping installing new apps and my free memory stay basically stable uner 80mb free space.
I have just one curiosity..if I go to Settings--> storage I see SD-ext "unavailable". After all I do not care much but if it is unavailable...where my apps have been stored so far? ps I reserved 1Gb of SD-ext .
Cheers
ps I just installed another apps of 3mb...no changes in the free space, so cool I feel like "no-limits"

stegal said:
...hello jm just coming back to thank you for your support. Finally I have a stable situation. Nevertheless after installing the script you have uploaded nothing changed. I had to factory reset, reinstal CM 4.3, install your script and everthing went smooth. Now it s 2 weeking I am keeping installing new apps and my free memory stay basically stable uner 80mb free space.
I have just one curiosity..if I go to Settings--> storage I see SD-ext "unavailable". After all I do not care much but if it is unavailable...where my apps have been stored so far? ps I reserved 1Gb of SD-ext .
Cheers
ps I just installed another apps of 3mb...no changes in the free space, so cool I feel like "no-limits"
Click to expand...
Click to collapse
not sure if it's been mentioned, but you should also be on cm7r2 hboot to maximise space (need to be s-off).
then follow the instructions on the first page of the thread to enable sd-ext. this will move user apps + user app dalvik cache to sd-ext. in other words, most of the dalvik cache should already be on sd-ext.
the dalvik2sd script should only move system dalvik cache to sd-ext, which will save you a little space.
to check everything is working, use an app like 'diskusage' to browse your partitions.