Develop Bugs

[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.

[ROM]JPM/JP6 "GoodBye RFS" ROM 0.2 (pre rooted, pre lagfixed, extremely experimental)

[ROM]JPM/JP6 "GoodBye RFS" ROM 0.2 (pre rooted, pre lagfixed, extremely experimental)
This is an ultimately experimental ROM. It might break your phone, cause headaches and data loss. This is only a showcase on how a ROM (mostly) without RFS(*) would work.
(*): this is only marketing bull****. The /efs partition still uses rfs in this rom.
This ROM contains knowledge from ChainFire, newmail, RyanZA, supercurio, ykk_five, ziggy (and me). Many thanks to them.
For the people who only care about scores and such:
Quadrant: 2006
Linpack: 14.501
Result of mount command:
Code:
/dev/block/stl9 on /system type [B]ext2 [/B](ro,noatime,nodiratime,errors=continue)
/dev/block/loop2 on /data type [B]ext2 [/B](rw,noatime,nodiratime,errors=continue)
/dev/block/loop1 on /dbdata type [B]ext2 [/B](rw,noatime,nodiratime,errors=continue)
/dev/block/stl11 on /cache type [B]ext2 [/B](rw,noatime,nodiratime,errors=continue)
For the people who actually care:
What is this?
This is a highly expermiental all-in-one lagfixed and rooted ROM based on JPM and JP6.
How to install?
You don't want to install this. Seriously... But you can find the DL link somewhere in this post if you're still curious. Simply open up Odin, use the contained pit, CSC, MODEM and PDA files, check re-partition, and wait.
It hangs after flashing at the initial boot screen (this was for version 0.1. Version 0.2 should boot up faster)
Yep, because it generates a 1.5GB large file, this takes around 3-4 minutes. It might also crash (shutdown, or switch to the battery loading screen) during this time, in case you have to reboot and try again. (or switch to a rom that's not experimental)
Hey, do I have to wait every boot? (this was for version 0.1. Version 0.2 should boot up faster)
Nope, only the first and second boot, and after each factory reset. (between the first and second boot there is a factory reset because of the CSC being applied by the recovery module)
Is this rom safe?
No. Moving near a melted nuclear reactor is safer than this.
Hey, this doesn't work / All my data is wiped / etc.
You've been warned.
For the technical people:
How?
Factoryfs.rfs was converted to ext2 on the phone prior flashing, and during flashing you actually flash "/system" as ext2 instead of rfs. Dbdata is empty, and will be replaced on the first boot, and cache.rfs was also converted to ext2 (so the csc files can be loaded on first boot), but will be actually reformatted on first boot. A pre-init script takes care of the cleaning up, and creating of ext2 partitions. The /data and /dbdata partitions are actually "dual-ext2'd" so they reside in a loop device which resides in an ext2 partition. The rationale behind this is to delay the fsync's which is the major cause of the lag. I also tried to do an "only ext2 without loop device" version, but that was useless (I've even got quadrant scores below 1k(!) with it). /cache is only single ext2'd however for recovery functions to work.
Everything is done by the /sbin/fs-patch.sh script. Feel free to check it. The script logs into the /res directory, you can check whether there were any problems during mount there (if you could actually boot of course...)
Why ext2?
The ext4 module compiled from the official sources do compile, do load, mkfs.ext4 does create the partition, but when mounting the phone drops a kernel panic. Until I can find an ext4 (or ext3) module that actually works there will be ext2 used, just to demonstrate that a no-rfs solution is actually working.
Why JPM/JP6?
You can find the rationale on the multinational ROM topic. This rom is actually the lagfixed version of that rom without the extras.
DL link:
0.1: http://android.sztupy.hu/dl/SztupY_JPM_JP6_NORFS_ROM_0.1.zip (on my server. Might be slow)
0.2: http://android.sztupy.hu/dl/SztupY_JPM_JP6_NORFS_ROM_0.2.zip (on my server. Might be slow)
Differences between 0.1 and 0.2:
0.1 uses rfs on the device + ext2 on a loop
0.2 uses ext2 on both the device and on the loop. 0.2 also has a much-much faster loop file creator utility (that creates the 1.8GB file in a second), so booting times should be normal again.
0.2 has higher quadrant scores (breaks the 2k barrier), but 0.1 felt more responsive (at least for me). I don't know anything about battery usage and such.
0.2 has problems with apps from the market, that install themselves on the sdcard. Hotfix
Links:
- scripts from initramfs

Appreciate you can post more comments about the problems and performance of this experimental ROM
Thanks for the great work!
Sent from my GT-I9000 using XDA App

this is exciting

Just threw this on my Captivate(since firmwares are semi-compatible), waiting for the ext2 partition to get created, and will report back. This is pretty awesome though, good work!

Thank you, looks very-very-very cool! Flashing now.

Great work.
Sent from my GT-I9000 using XDA App

Excellent work! Can you make a version that makes the /data partition native ext2 instead of a loop device? Thanks!

Woah, great stuff, though I'm not gonna try it, sounds to dangerous. I've been using your other ROM and lovin' it, thanks!

Hey sztupy, good work man... cant wait to see the first reports...

Linpack: 14035
What?!?

anyone has any success loading this rom? i was being curious, i tried flashing on my phone, but kept restarting and looping at the initial Galaxy S GT-i9000 screen.
by the way the linpack score, is it 14035 or its just missing a decimal point? lol!

giantdroid said:
anyone has any success loading this rom? i was being curious, i tried flashing on my phone, but kept restarting and looping at the initial Galaxy S GT-i9000 screen.
by the way the linpack score, is it 14035 or its just missing a decimal point? lol!
Click to expand...
Click to collapse
Try to reflash it using Odin. That's what I did and it's running now
I'm getting 14.211 mflops in 5.9 secs

What languages are in swype ?
Does it contain romanian ?

how is the stability so far, for you that have tested it? and screw the scores. How is the feeling? any lagg? anything?

Nice one! Has anybody had any issues with /system being EXT yet? I'm guessing not, but this is going straight on my phone anyway!
EDIT: noatime,nodiratime performs a lot better than relatime btw
Why is /data on loopback on top of RFS? Seems silly!
You should have done /data as a loopback on top of /dbdata EXT2 for extreme speed! Do it!

Just installed this ROM/Kernel...
Setup and Flashing went without any hitch. The first boot was longer than usual, but as it was forewarned..so no surprises there.
I will give it a thorough test today and post the issues here, if any.
Thank you for this amazing work.

lealdud1 said:
how is the stability so far, for you that have tested it? and screw the scores. How is the feeling? any lagg? anything?
Click to expand...
Click to collapse
No Lag at at all. This is by far the ZIPPIEST ROM I have tried...(without any lag-fix installed)
I agree, screw the scores...it's the feel and the response that matters and this ROM is just great at it.
Haven't used it much but no FC or any other errors...so far, so good.

RyanZA said:
Nice one! Has anybody had any issues with /system being EXT yet? I'm guessing not, but this is going straight on my phone anyway!
EDIT: noatime,nodiratime performs a lot better than relatime btw
Why is /data on loopback on top of RFS? Seems silly!
You should have done /data as a loopback on top of /dbdata EXT2 for extreme speed! Do it!
Click to expand...
Click to collapse
I'll definatly give this rom a try when this ^ has been done and when a few more ppl have tested it without to many issues.
Thanks in advance for all your work on this rom guys, I love your other rom sztupy.

Sounds very exciting! Will probably wait until you manage to get /data as ext2 to give it a try. Still, well done with this!

will try on saturday...just to see if any further "improvement" will crop up by then
thank you sztupy for putting this out here!

[ROM] FroyoB Hercules V4 Final -18/7/11 Released

FroyoB Hercules V4 Final
This ROM is based on tiad8 new rom - thanks tiad8.
Changes:
changed back to old fonts!!!
add new launcher 2.3.3.
add new market.
changed phone - thanks to cytown from XDA.
changed theme.
some bug-fixing...
What works:
* SuperUser
* WiFi
* GPS
* 3G Network
* GPS
* Phone (new)
* SMS
* Good Battery Life
* camera
* camcorder
* new market
* youtube
How to install:
A. Download:
V1: http://www.multiupload.com/ZSOG83Q1K7
V2: http://froyob.blogspot.com/2011/07/froyob-hercules-v2-final-release.html
V3: http://froyob.blogspot.com/2011/07/froyob-hercules-v3-first-beta-release.html
V4: http://froyob.blogspot.com/2011/07/froyob-hercules-v4-final_18.html
B. Before install :
1. Format your SDCARD make 4 Partition with recommended size:
1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)
Be sure make all 4 partition primary
2. extract and copy folder npkboot to root of sdcard and put in kernel that you like (I use kernel 1295 on my Raphael and it very good).
3. copy FroyoB_Hercules.zip in to root of sdcard.
C. Install:
1. run Haret, and wait when it will be asked to press "Volume Down" shortly (!!important!! shortly) to launch
ClockworkMod Recovery or any other key to usually continue booting into Android.
Press volume Down and wait for menu Recovery.
2. In menu recovery choose "install zip from sd-card" choose zip from sdcard and select "FroyoB_Hercules_V2_final.zip"
Confirm installation . after installation finish, Confirm installation then back to main menu (press ok key) and
choose: reboot system now.
3. Run HARET again and boot into Android.
when you report a bug please do it in this format:
1. my device is:
2. I'm using kernel:
3. I'm using Ver:
4. What CWM Ver:
5. the problem is:
thanks
Nebarkay

anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try

loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
The four partitions are laid out..
"1st partition: FAT32 (sdcard / Rest)
2nd partition: EXT2 (system / 300MB )
3rd partition: EXT2 (data / 300MB)
4th partition: EXT2 (cache / 300MB)"
However, cache is not necessary - especially not 300mb. I think neopeek recommended 50mb, but I don't think it's necessary at all.
Other builds in this section of the forum require only one FAT32 partition. This is because the data & system are just loop mounted.

For creating partitions I recommend this:
MiniTool Partition Wizard Home Edition
http://www.partitionwizard.com/free-partition-manager.html
it's free and very useful

loni90 said:
anyone tested this?
im coming from HD2, and wondering why you need all the 4 diffrent partitions? which program do you recommend to do this?
can you post any screenshots? would like to see before i go ahead an try
Click to expand...
Click to collapse
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")

maff1989 said:
EASEUS Partition Master Home Edition for Windows is the fastest tool I've used. Haven't had any problems.
You need the partitions on your SD card because this ROM is in CWM format and will install to those EXT2 partitions (/system, /data, /cache). The order must be:
1. FAT32 (FAT32)
2. /system (EXT2)
3. /data (EXT2)
4. /cache (EXT2)
BE SURE TO REMOVE THE "/" WHEN NAMING THE PARTITIONS!! (I.E. "system", not "/system")
Click to expand...
Click to collapse
EASEUS is fantastic, I forgot it did ext2 as well. I use it to resize NTFS partitions all the time!

Can anyone confirm it working on Sprint TP2? and what does and does not work?
Thanks guys!

I installed on a Sprint TP2 last night but haven't really had a chance to drive it full throttle. Did try turning on BT unsucessfully. Getting longer life than FRX06 so far. Usually I have to charge before my 8 hour shift is done. Today I was able to go 11 hours with moderate use and still had 68% showing on the meter when I had a reboot to windows while trying to update an app. We'll see how it goes the next few days now that all of my apps are installed thanks to TB.

i keep on getting an issue with no signal. I did all the steps successfully but when it loads i get no signal. and then on reboot i get signal. I rebooted once again and now i have no signal what so ever. am i missing a step?

been using this for a couple of days...
device: at&t tilt 2
kernel: wistilt2
testing period: 3 days
battery: one full day... charge all night
signal... weak at times
system speed: awefully slow... worse then looped
3d: not terrible not great.. to be expected
conclusion: not for me.. too slow.. spotty signal... not the best battery life.. have seen better...

ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?

loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
Closest to stock and Sense do not go together. Sense is an abomination, horrid UI for Android. I don't get why it made WinMo so great but Android so horrid.
I recommend FRX06 myself, 07 is going to be out soon (promise!)

loni90 said:
ok, now i know.
but i want to fix android to my lil´brothers TP2, and wondering what ROM i should use? which one is the most stable, and complete - and closest to stock? any good HTC sense roms?
Click to expand...
Click to collapse
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...

Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks

villa15 said:
I would very much love to give ur gingerbread build a try, so if u could please send me a zip as well. Thanks
Click to expand...
Click to collapse
Actually I'm having one small problem... the android marketplace is only displaying like a few hundred apps...
I need to do some more research to find out why... so if you want me to fix it first or there are quite a few alternative marketplaces u can install... one I use on it right now is called--- 1 mobile market...
If you don't care I will send u the zip to try... it has gapps...
Just pm your email address

sooo, been testing this for a few days on my Rhod100... and have to say it pretty much sucks...
signal drops to 0 quite often, i get random reboots when trying to call someone / in call / when hanging up, apps that use the inet connection force close when i lose data connectivity (meebo, xda, gmail), the font is _horrible_ (yes i know, fontchanger is included, but it doesnt work the way one would expect it to)
to sum it up, it's like a F1 car without a steering wheel.. fast, fun for the first minute, but completely useless
going back to FRX06 looped and finally deleting NP from my favs
edit : forgot to mention the new audio code isnt integrated, so you cant use the new .39 kernel, but thats just the icing on the ****cake

Trekfan422991 said:
i have a really nice version of gingerbread that i am modifying... i will send you a zip if you want to try...
Click to expand...
Click to collapse
I would like to get it too. Thanks!

thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?

bahaa87 said:
thanks for this rom
but when I started haret.exe file and press Run botton, I saw this message:
that default.txt doesn't found
what's problem?
Click to expand...
Click to collapse
You have to choose your startup.txt according to your device,there should be a folder called startup,check inside for your device and copy it where there's haret.exe

Thank you I tried the ROM on 1 / 7 is good and where some of the problems
I will work on this

*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] CM9 with INT2EXT+: GooglePlay download problems

Hallo,
I am working with the stable CM9 version and INT2EXT+ on my HTC Wildfire S which you really cannot use without any 'storage expanding' script.
Its storage space is so horrible low. So thank you for this solution very much.
The mentioned constellation is running fine and fast so far - just the opposite to ROM EQDKP (with Data2SD) I had before which was stable but EXTREMLY slow!! (only the akku state makes problems obviously at all CM versions as it does not seem to be correct (lack of refresh)! Unfortunately.)
There is still enough space on my SD card:
* Phone info -> partition info: 724 MB used from 1,08 GB (data folder)
* Apps -> All: 683 MB used, 421 MB free
* Storage -> internal storage: 782 MB Apps, 380 MB free.
Who knows why they are different but anyway they say about the same.
But now I have a GooglePlay download problem when I want to install apps bigger than 12 MB. (before (when I did not have so many apps installed) this never was a problem)
To say it clearly: it is NOT an installation problem but happens already during the app download. It just stops and says that there is not enough internal phone storage left. VERY strange!
I doubt that this has to do s.th. with a cache space, does it? But this would be the space used for downloads, right?
[partition info -> cache: 2,5 MB / 35 MB; pi -> system: 211 MB / 260 MB)
But why should it make problems then? Can this be a problem of the script / INT2EXT ??...
I would be glad to get hints from anybody what the real problem here could be.
Thank you very much!

Falk2 said:
Hallo,
I am working with the stable CM9 version and INT2EXT+ on my HTC Wildfire S which you really cannot use without any 'storage expanding' script.
Its storage space is so horrible low. So thank you for this solution very much.
The mentioned constellation is running fine and fast so far - just the opposite to ROM EQDKP (with Data2SD) I had before which was stable but EXTREMLY slow!! (only the akku state makes problems obviously at all CM versions as it does not seem to be correct (lack of refresh)! Unfortunately.)
There is still enough space on my SD card:
* Phone info -> partition info: 724 MB used from 1,08 GB (data folder)
* Apps -> All: 683 MB used, 421 MB free
* Storage -> internal storage: 782 MB Apps, 380 MB free.
Who knows why they are different but anyway they say about the same.
But now I have a GooglePlay download problem when I want to install apps bigger than 12 MB. (before (when I did not have so many apps installed) this never was a problem)
To say it clearly: it is NOT an installation problem but happens already during the app download. It just stops and says that there is not enough internal phone storage left. VERY strange!
I doubt that this has to do s.th. with a cache space, does it? But this would be the space used for downloads, right?
[partition info -> cache: 2,5 MB / 35 MB; pi -> system: 211 MB / 260 MB)
But why should it make problems then? Can this be a problem of the script / INT2EXT ??...
I would be glad to get hints from anybody what the real problem here could be.
Thank you very much!
Click to expand...
Click to collapse
That's because of the script(INT2EXT+), it keeps the data/data in the internal memory. This will give you more speed but if it is filled you won't be able to install or download anything from the Play Store. That's the reason why you are not able to use your EXT partition completely. If you want more space for apps, try INT2EXT4. But you will have to sacrifice some speed if you use it

Hallo csoulr666,
thanks for your helpful feedback!
Aha, but I would have expected an error message only during installation but not during download already which uses just the cache, doesn't it???...
Maybe you refer to the sentence of the INT2EXT script author: "100mb internal is needed for every 500mb sd-ext"!?
Is it this what you mean?...
But I still have much more than 200 MB left (380MB)!!... That should not be the reason then!?...
(and again: he talks about the internal state memory but not about the cache which is reserved ANYWAY, isn't it?...
How can I find out how much data is left in the original internal memory???...
And why are there differences in memory above (284, 421, 380 MB)?...
*****************
But if it once should be for sure that the internal memory is the reason for that I would prefer to change the 1 GB sd-ext partition to 1,5 GB by 'Minitool Partition Wizard'. Should work,shoudln't it?...
Or do you think the difference in speed is not that much!?...

However, Root Explorer tells me for data/data:
used 130,66 MB, free 19,34 MB. (unfortunately cannot see folder sizes!)
Hmmmh... so now I understand nothing anymore!!
Should I at the end add 200 MB + 130,66 MB ?...

Falk2 said:
Hallo csoulr666,
thanks for your helpful feedback!
Aha, but I would have expected an error message only during installation but not during download already which uses just the cache, doesn't it???...
Maybe you refer to the sentence of the INT2EXT script author: "100mb internal is needed for every 500mb sd-ext"!?
Is it this what you mean?...
But I still have much more than 200 MB left (380MB)!!... That should not be the reason then!?...
(and again: he talks about the internal state memory but not about the cache which is reserved ANYWAY, isn't it?...
How can I find out how much data is left in the original internal memory???...
And why are there differences in memory above (284, 421, 380 MB)?...
*****************
But if it once should be for sure that the internal memory is the reason for that I would prefer to change the 1 GB sd-ext partition to 1,5 GB by 'Minitool Partition Wizard'. Should work,shoudln't it?...
Or do you think the difference in speed is not that much!?...
Click to expand...
Click to collapse
What the author meant that you need a 100MB of "acutal" internal storage(not EXT partition) to be able to use about 500 MB of the EXT partition. That's actually an estimate value, so you won't be able to get the same figures in all the ROMs. Even before downloading, the Play Store checks for the storage available for all the parts of an application. Maybe that's why it returns errors

Hallo csoulr666,
thank you for your additional explanation. In fact this would explain the phenomena.
I calculate then:
About 100 MB internal memory I need for 100 MB.
As WFS has about 120 MB internal mem. it is about 650 MB at all. Correct?
So this is the limitation ia have then which is too early.
And do you know if I can read out the left or too low memory anyhow.
Means, does any value gives me an information about the left actual internal memory value?
Possibly no?...
So then I am thinking about a change of the memory script.
Did you or anybody else can answer the following questions?:
1.) Do I have more memory left with scripts like Link2SD, INT2EXT or INT2EXT4 ??
2.) Is the speed reduction remarkable here? And if so when exactly?
3.) How can I change over to another script without reinstalling the whole ROM? (no overwriting possible, is it?)
Thank you very much again for your feedback!!

Falk2 said:
Hallo csoulr666,
thank you for your additional explanation. In fact this would explain the phenomena.
I calculate then:
About 100 MB internal memory I need for 100 MB.
As WFS has about 120 MB internal mem. it is about 650 MB at all. Correct?
So this is the limitation ia have then which is too early.
And do you know if I can read out the left or too low memory anyhow.
Means, does any value gives me an information about the left actual internal memory value?
Possibly no?...
So then I am thinking about a change of the memory script.
Did you or anybody else can answer the following questions?:
1.) Do I have more memory left with scripts like Link2SD, INT2EXT or INT2EXT4 ??
2.) Is the speed reduction remarkable here? And if so when exactly?
3.) How can I change over to another script without reinstalling the whole ROM? (no overwriting possible, is it?)
Thank you very much again for your feedback!!
Click to expand...
Click to collapse
Actually the usable space depends on the internal memory that is free. So it will vary from different ROMs.
1) You would have more space with INT2EXT, INT2EXT4 but not with Link2SD(unless you buy the PRO version of the app allowing to move everything to the EXT partition)
2) Speed reduction can be significant if you load it up with a lot of Apps. And it might get a little annoying after 2-3 weeks or so
3)Overwriting will not be possible in most cases, since different scripts might mount different things on the 2nd Partition

back again from holiday...
So what would you suggest what I can do?
To 1: How much memory do I win in average with INT2EXT or the others? Can I install e.g. double the number of apps then?...
To 2: Your answer stands for which scripts? All the three? Or only INT2EXT, INT2EXT4 maybe?...
Could you explain why exactly the speed reduction appears? (isn't the fix part of an app also loaded in the fast RAM when started. So isn't it more a question of available RAM than speed?...)
To 3: Changing to another script would mean to flash the whole ROM again?... Or isn't there a way to delete my actual INT2EXT+ before installing e.g. INT2EXT?... Or is there still another way to exchange my script??...
4.) At last I couldn't even start my mobile at all! Although I did not install any new app for months all background provesses (like GooglePlay) cannot be started. Is this maybe because of updates of installed apps?...
Anyway I deinstalled TripAdvisor which needed full 45 MB ( and cannot be moved to SD card at all). But this did not help at all (reboot done)! I still have the same memory problems now and now cannot run my ROM CM9. Why not? Why the deinstallations don't help??...

Falk2 said:
back again from holiday...
So what would you suggest what I can do?
To 1: How much memory do I win in average with INT2EXT or the others? Can I install e.g. double the number of apps then?...
To 2: Your answer stands for which scripts? All the three? Or only INT2EXT, INT2EXT4 maybe?...
Could you explain why exactly the speed reduction appears? (isn't the fix part of an app also loaded in the fast RAM when started. So isn't it more a question of available RAM than speed?...)
To 3: Changing to another script would mean to flash the whole ROM again?... Or isn't there a way to delete my actual INT2EXT+ before installing e.g. INT2EXT?... Or is there still another way to exchange my script??...
4.) At last I couldn't even start my mobile at all! Although I did not install any new app for months all background provesses (like GooglePlay) cannot be started. Is this maybe because of updates of installed apps?...
Anyway I deinstalled TripAdvisor which needed full 45 MB ( and cannot be moved to SD card at all). But this did not help at all (reboot done)! I still have the same memory problems now and now cannot run my ROM CM9. Why not? Why the deinstallations don't help??...
Click to expand...
Click to collapse
1. You will definitely be able to install more apps, but the exact number depends on the apps you use.
2. (2) stands for the difference between INT2EXT/INT2EXT4 and INT2EXT+
3. You simply can't change scripts, you will have to make a clean install and then use another script.
4. That happens sometimes, I generally reflash the ROM to get rid of this.

thank you vrey much, csoulr666, for answering !!
Unfortunately there are still answer details left...
To 1: What is it that makes the space bigger? Isn't it just the data part which normally is very low? (s. www.xda-developers.com/android/cronmod-gives-users-options-of-a2sd-d2ext-int2ext) So I suppose that there would be no big win of space with INT2EXT instead of INT2EXT+. What do you say?
1b.) How can I measure/read and estimate the left telephon space which is too small/missing in my case? (you know, all my storage values are okay currently but I have this problem anyway!)
1c.) What happens if I move apps to SD card by Options/Apps although INT2EXT+ is working?... And can this help?
T0 2: Again, could you please explain why exactly the speed reduction appears? I don't understand this. (isn't the data part of an app also loaded in the fast RAM when started. So isn't it more a question of available RAM than speed?...)
To 3: This is very bad news. It would mean much work for me if I really had to reinstall the ROM.
So are you pretty sure? Did you try already? I e.g. could imagine that there might be an extra transfer/exchange script from the author. Or a script exchange is already supported by the scripts. Oe.
See, the INT2EXT would also move the data part. So as this is NOT done yet (INT2EXT+) the new script (INT2EXT) would just have to complete this by moving them also to SD. I would imagine that this should work, shouldn't it?
3b.) Do you know where the script is located?... And shouldn't a new flash just overwrite it (both are very simular anyway!)? (maybe it can be done manually as well??...)
To 4: Isn't that strange? How can that happen? Why do you say 'sometimes'? Own experiences?
What can be the reason for this sometime problem?... How can I double-check that? Or is there maybe any option necessary to say the system to re-read the storage values?... Or... Who else can I ask?
Which phone do you have and which scripts did you try already?
If you cannot answer some questions... Can I reach the writer of the INT2EXT scripts maybe?... (if I may write him under [email protected] ?...)

Hallo csoulr666,
are you still there?
Would be so nice to get a feedback from you.
Or are you helpless now as well?...

Falk2 said:
thank you vrey much, csoulr666, for answering !!
Unfortunately there are still answer details left...
To 1: What is it that makes the space bigger? Isn't it just the data part which normally is very low? (s. www.xda-developers.com/android/cronmod-gives-users-options-of-a2sd-d2ext-int2ext) So I suppose that there would be no big win of space with INT2EXT instead of INT2EXT+. What do you say?
1b.) How can I measure/read and estimate the left telephon space which is too small/missing in my case? (you know, all my storage values are okay currently but I have this problem anyway!)
1c.) What happens if I move apps to SD card by Options/Apps although INT2EXT+ is working?... And can this help?
T0 2: Again, could you please explain why exactly the speed reduction appears? I don't understand this. (isn't the data part of an app also loaded in the fast RAM when started. So isn't it more a question of available RAM than speed?...)
To 3: This is very bad news. It would mean much work for me if I really had to reinstall the ROM.
So are you pretty sure? Did you try already? I e.g. could imagine that there might be an extra transfer/exchange script from the author. Or a script exchange is already supported by the scripts. Oe.
See, the INT2EXT would also move the data part. So as this is NOT done yet (INT2EXT+) the new script (INT2EXT) would just have to complete this by moving them also to SD. I would imagine that this should work, shouldn't it?
3b.) Do you know where the script is located?... And shouldn't a new flash just overwrite it (both are very simular anyway!)? (maybe it can be done manually as well??...)
To 4: Isn't that strange? How can that happen? Why do you say 'sometimes'? Own experiences?
What can be the reason for this sometime problem?... How can I double-check that? Or is there maybe any option necessary to say the system to re-read the storage values?... Or... Who else can I ask?
Which phone do you have and which scripts did you try already?
If you cannot answer some questions... Can I reach the writer of the INT2EXT scripts maybe?... (if I may write him under [email protected] ?...)
Click to expand...
Click to collapse
1. What happens is that the internal memory is moved and linked to the 2nd partition you created on the SDcard. The scripts vary on the basis of what parts of the memory(system files, data files) are being transferred and how it is transferred to the EXT partition.
1b. I can't seem to estimate the storage left in any way I tried, so can't help you there.
1c. This COULD help, but I'm not quite sure about that.
2. The SDcard has a slower speed as compared to the Flash memory on your phone. INT2EXT+ tends to rectify this by leaving the app data(/data/data) on the internal memory. So if the app data size reaches close to the actual internal memory, you will get low memory errors.
3. As I mentioned in 1 above, the scripts vary on how the linking is done, so it would only make it worse if you just remove the script and add a new one.
3b. The scripts are located in "/system/etc/init.d". See 3 above for the rest of the answer.
4. I have never been able to find the solution to the problem, too much apps, script causing problems.......... I don't know.
My phones are mentioned in the Signature. I have tried nearly every EXT script(Link2sd, INT2EXT,INT2EXT+, mount2sd etc) with the WFS.

thank you again for your good and detailed explanations and your patience!!
To 1): Okay, thank you anyway. In average it seems as if the limitation ist just about 700 MB for WFS. And if all data files are transferred to the SD card the internal storage will not be filled at all, right? So the space for downloaded apps seems to be limited only by the size of the SD card, right? Remark: Would be perfect if it could be selected during app installation where the data sector of the app should be transferred to. But this does not seem to be possible by a script, is it?...
To 2): Okay, that's what I know - the much slower SD card. I mean how can I estimate if an app which uses data files needs to access them often or not?... Would be good if I could estimate that before I use/choose an app.
To3): Okay, understand. However I did it, overwriting the old script. Booting was possible but there was no change at all.
4.) You wrote that you tried so many scripts... So which is your conclusion? Which INT2EXT script do you use today?...
4b.) And is there any reason why there is no script INT2EXTV2 (without '+')? Cause I would like to use Linux swap and need more than 750 MB memory for my downloaded apps.
Or where can I get this script maybe ?...
Another problem I have...
5.) I tried to install the actual CM11 (cm-11-20141004-NIGHTLY-marvel) with INT2EXT but I cannot boot again after I additionally flashed GAPPS (Gapps-KK-4.4.0-Signed): endless loading. (I followed the original installation instruction!!)
How can that be? I suppose that the reason is that my storage size for the system part is too low. But the email app is already missing in this ROM... Isn't that strange? Did this happen to you as well already?... What can I do?...
5b.) Now I am in the situation that I can choose between CM9, CM10 and CM11. Which one would you suggest most?
Remark: CM11 seems to make problems and e.g. its storage management does not work: at 'Android options/storage' it does not show the sizes (endless calculation...), launcher is more circumstancial, etc. Up to now I used CM9 which worked quite well - but it is old. Maybe CM10?...
Or isn't it the most actual one? How can I find?...
Thank you again for your good feedback!!

Falk2 said:
thank you again for your good and detailed explanations and your patience!!
To 1): Okay, thank you anyway. In average it seems as if the limitation ist just about 700 MB for WFS. And if all data files are transferred to the SD card the internal storage will not be filled at all, right? So the space for downloaded apps seems to be limited only by the size of the SD card, right? Remark: Would be perfect if it could be selected during app installation where the data sector of the app should be transferred to. But this does not seem to be possible by a script, is it?...
To 2): Okay, that's what I know - the much slower SD card. I mean how can I estimate if an app which uses data files needs to access them often or not?... Would be good if I could estimate that before I use/choose an app.
To3): Okay, understand. However I did it, overwriting the old script. Booting was possible but there was no change at all.
4.) You wrote that you tried so many scripts... So which is your conclusion? Which INT2EXT script do you use today?...
4b.) And is there any reason why there is no script INT2EXTV2 (without '+')? Cause I would like to use Linux swap and need more than 750 MB memory for my downloaded apps.
Or where can I get this script maybe ?...
Another problem I have...
5.) I tried to install the actual CM11 (cm-11-20141004-NIGHTLY-marvel) with INT2EXT but I cannot boot again after I additionally flashed GAPPS (Gapps-KK-4.4.0-Signed): endless loading. (I followed the original installation instruction!!)
How can that be? I suppose that the reason is that my storage size for the system part is too low. But the email app is already missing in this ROM... Isn't that strange? Did this happen to you as well already?... What can I do?...
5b.) Now I am in the situation that I can choose between CM9, CM10 and CM11. Which one would you suggest most?
Remark: CM11 seems to make problems and e.g. its storage management does not work: at 'Android options/storage' it does not show the sizes (endless calculation...), launcher is more circumstancial, etc. Up to now I used CM9 which worked quite well - but it is old. Maybe CM10?...
Or isn't it the most actual one? How can I find?...
Thank you again for your good feedback!!
Click to expand...
Click to collapse
1) I think so, but considering not much of the files are transferred, it will make a slight difference instead of a big one. And no, all the scripts I know of do not provide the option to select the sector to install to during the installation of an app. That would actually defeat the purpose of the script to be easy to use. Beginners will have a hard time if they are provided with millions of options.
2) I don't think you can estimate that. You will then need to create estimates for every kind of app(and there are a LOT kinds of them)
3) Overwriting a script with another would either not work or will cause problems.
4)I was using INT2EXT4 recently but will not use anymore scripts because the WFS isn't my primary device anymore. So I don't require much apps to be installed on it.
4b) You will have to ask the developer of the scripts that. He will clear you on that more.
5) That could be because of the Gapps, what was the size of the Gapps you installed? If you are using the one from Goo.im or PA's site then you need to switch to a lite version of Gapps.
5b) I personally use CM9 or CM10.1 if I want stability. CM10 has it's fair share of bugs since it hasn't received as much time as the CM 9 and 10.1. In then end it is upto you to decide which ROM suits you more.

to 1.) I think Link2SD is supporting this (selected data location)... It is easy to handle (you decide once just before installation of an app)!
to 4.) Have you been satisfied with INT2EXT4 ? Maybe it is not my last change from EXT3 to EXT4, I don't know... But my CM11 version now runs in some way unstable. S. below.
to 4b.) I asked Croniccorey already but unfortunately he did not answer yet...
to 5.) Gapps-KK-4.4.0-Signed is said to be already a lite version. So I cared for that. The size: 15.2 MB. Is that okay? If so then we have a strange problem here, don't we?
Meanwhile I did the following: I did not flash both (Rom AND INT2EXT4 script) within one boot as advised everywhere. And this time GooglePlay suddenly appeared. It seems to be included in the Rom but before (Rom and script in ONE boot) did definitly NOT appear. Strange, isn't it?...
So this time it was not necessary to flash GAPPS so that this problem was shipped around.
But this CM11 with INT2EXT4 (before CM9 and INT2EXT+ which was quite fast and stable (but limited to 720 MB Apps)) is not that stable AND boots at least double the time than CM9!!
During installation/configuration of CM11 and lots of apps there were a lot of crashes. E.g. I started Skype four times or GoogleMaps twice (after installation) before they did not crash during their start.
I wanted to give up already but after all that it now the apps which need big resources run acceptable.
Now they crash only when there are too much processes at one time. E.g. if more than 4 pictures of WhatsApp (which s.o. has sent to me) are loaded. Or if there is a heavy background process running and I scroll some content of another app.
I doubt if this is what you ment with unstable (of CM11)!?
6.) Do you have any idea where this kind of unstability comes from?...
And which kind of unstability did you realise at CM11?...
But again, maybe it is just my change from EXT3 to EXT4. Maybe I did not select the right settings, like cluster size, ...!?

would be perfect if you or s.o. else would comment my experiences soon.
I really don't know right now what is normal here and what I would have to accept so far...

meanwhile I could answer my questions and problems by myself by long tries, as nobody seemed to know it here...
To 1.) Yes, Link2SD seems to be just the same as INT2EXT scripts (but here you need to pay for a none-'+'-version: app data are only linked to SD with Link2SD plus version) but you can control at each installed app if also app DATA are moved to SD or not. And you have a comfortable UI where you can manage everything. You can even switch off the linking. At INT2EXT there is no chance: if you want to change anything you have to reinstall your whole ROM !!
To 2.) I could not realise a very remarkable reduction of speed between INT2EXT4+ and INT2EXT4. Sometimes the start or change of apps (taskmanager) was a bit slower. So if you use a class 10 SD card and you want no app installation limitations I suggest not to use the INT2EXT plus version. Maybe the solution is LINK2SD anyway!...
To 3.) The perfect solution here is the app Link2SD (s. GooglePlay).
To 4.) My CM11 ROM now runs stable. Solution: I reinstalled it and flashed it with 'SuperWipeMarvelEdition' first. Really unbelievable but that helped!
To 5.+6.) Also these problems were solved with 'SuperWipeMarvelEdition'. Now the flashing of GAPPS worked fine.
To 5b.) My CM11 version runs also quite well. It might be a bit slower but not much. But it is quite big and lots of system functions are missing. E.g. Google Weather & News, Email, Talk, etc. Its GAPPS is too small. An INT2EXT PLUS version is impossible here as you have just 30 MB internal storage left! You have to search for all the apps and install them additionally. Unfortunately I could not find any pool where all those missing apps are collected for download. Very sad! Does anybody know?... (what I found only: http://forum.xda-developers.com/showthread.php?t=1917411 )
Point 4b) I still could not answer. Nobody seems to know and Croniccorey unfortunately does not give any life sign...