Originally Posted by croniccorey

Unknowen please post.your resault

Sent from my HTC Desire using xda app-developers app

I have tried it on JB. It works but it drastically reduces performance!

Originally Posted by andreasf93

I have tried it on JB. It works but it drastically reduces performance!

really? I'm seeing no performance issues with this on JB (moto defy+) ... using INT2EXT+

My phone has way to low memory, I can only use A2SD mod :<

Originally Posted by pepcisko

First of all, thank you croniccorey for your work - the INT2EXT+ script is amazing.
But here's a question. How does it behave when upgrading ROMs? Example:

- I inserted the script directly into a custom ROM that is being developed for my phone
- formatted the SD-EXT (ext2) partition in CWM recovery
- to be sure I don't mess up anything, I did a full wipe (data/cache/dalvik), installed the ROM and the INT2EXT+ script was working great
- today a new ROM nightly came out, so I inserted the script again into the ROM, flashed it via CWM recovery, cleared dalvik/cache
- after reboot, it's not moving out of bootanimation

Any clue what could be wrong? Thank you..

---------- Post added at 09:25 PM ---------- Previous post was at 08:32 PM ----------

Update - I guess it's really something with the script. I wiped the data again, formatted the EXT partition and the fresh nightly ROM started nicely with the INT2EXT+ script. Not sure what the problem could be.. please advise.

in what rom on what phone

Originally Posted by andreasf93

My phone has way to low memory, I can only use A2SD mod :<

why only a2sd if you have low mem you should flash a int script as they give the most space, in my opinion int2ext+ is the best and if you wanted to use it and not get problems just make sure the for every 500mb of ext you have, there is 100mb of internal space and it will work great

Originally Posted by croniccorey

why only a2sd if you have low mem you should flash a int script as they give the most space, in my opinion int2ext+ is the best and if you wanted to use it and not get problems just make sure the for every 500mb of ext you have, there is 100mb of internal space and it will work great

But I have ~150MB (free) internal after a ROM install and I am already at 600MB apps usage on sd-ext

Sent from my fiery Galaxi Mini!

Originally Posted by andreasf93

But I have ~150MB (free) internal after a ROM install and I am already at 600MB apps usage on sd-ext

Sent from my fiery Galaxi Mini!

You could have upto a 750mb ext then or you could try int2ext and nothing is on internal you can have as big an ext as you want but may cause lag on slower sdcards

Sent from my HTC Desire using xda app-developers app

Originally Posted by croniccorey

in what rom on what phone

phone/ROM is always in the signature moto defy+, CM10 unofficial nightly

Originally Posted by pepcisko

phone/ROM is always in the signature moto defy+, CM10 unofficial nightly

Does it boot or loop and make sure the script is named 40int2ext also try to flash The script over the rom to be sure it is defently not working aside from that you could make sure there's no other scripts that are mounting the ext and check to see what was changed in the update If all of this fails send me a logcat aswell as the ouput of the 'df' command

Sent from my HTC Desire using xda app-developers app

Originally Posted by croniccorey

Does it boot or loop and make sure the script is named 40int2ext also try to flash The script over the rom to be sure it is defently not working aside from that you could make sure there's no other scripts that are mounting the ext and check to see what was changed in the update If all of this fails send me a logcat aswell as the ouput of the 'df' command

It seems to be stuck, usually a bootloop is "visible" via the notification led blinking occassionally, but here it's not the case, the phone just doesn't move out of the bootanimation. Script is named correctly. Actually there is a 05mountsd script (attached) that tries to mount the sd-ext partition and it's run prior to the 40int2ext script and apparently it tries to mount the ext partition as ext3 fs. Could this be the problem? Since in the 40int2ext script you're unmounting it prior to doing your magic, I'm not sure. As for the updates, the init.d folder is still the same and the int2ext script works fine if I do a data wipe. It just doesn't like (or is not liked by) the ROM update.

Df output:

~ # df
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   243660        48    243612   0% /dev
/dev/block/mmcblk1p21
                        332946    323455      9491  97% /system
tmpfs                   243660        48    243612   0% /dev
tmpfs                   243660         0    243660   0% /mnt/asec
tmpfs                   243660         0    243660   0% /mnt/obb
/dev/block/mmcblk1p24
                        198335      5835    192500   3% /cache
/dev/block/mmcblk1p25
                       1299160     86460   1212700   7% /sd-ext
/dev/block/loop7          4026      1158      2868  29% /pds
/dev/block/mmcblk0p2   8182564     79944   7686940   1% /data
/dev/block/mmcblk1p25
                       1299160     86460   1212700   7% /data/data
/dev/block/mmcblk1p25
                       1299160     86460   1212700   7% /data/property
/dev/block/vold/179:1
                      54037440  19853600  34183840  37% /mnt/sdcard
/dev/block/vold/179:1
                      54037440  19853600  34183840  37% /mnt/secure/asec

logcat

I/mountsd ( 2169): Checking filesystems..
I/run-parts( 2140): e2fsck 1.41.11 (14-Mar-2010)
I/run-parts( 2140): /dev/block/mmcblk0p2: clean, 346/1040384 files, 52769/2078409 blocks
I/run-parts( 2140): mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: Invalid argument
E/mountsd ( 2174): Unable to mount filesystem for /sd-ext!
I/run-parts( 2140): umount: can't umount /sd-ext: Invalid argument
I/run-parts( 2140): umount: can't umount /sd-ext: Device or resource busy
I/run-parts( 2140): Starting Automatic ZipAlign
I/run-parts( 2140): ZipAligning ro.hex.installers.mc-1.apk
I/run-parts( 2140): Automatic ZipAlign finished

---------------------

actually the mount failure seems to be a problem in the ROM's script, I contacted the dev about it.