yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] BleedingIris:
Hi I'M Running the script only version of m2sd on my Rom. Can I upgrade to the latest version and app without ruining my original configurations without loss of data, or reboots (without having to install apps all over again)?

[apps linked, dalvik linked,data not linked(linked with titanium ),cm cache to data enabled,mtd device]

Can I preconfigure with the app itself? Or should I do with scripts again?

Thanks.

cm9b11/mcm9b3 htc a310e

---------- Post added at 02:05 AM ---------- Previous post was at 02:00 AM ----------

I have the data/m2sd folder. Is it enough if I just copy that to the new version?

My m2sd binary is missing though... not sure what happened?

cm9b11/mcm9b3 htc a310e
[Android Software/Hacking General [Developers Only]] impactor:
I'm already using the newest version. Had the same issue in the previous one.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Just install the app from play store, let it install the script, configure your options and then reboot.

If you install the zip in recovery without having the new configurations, the script will use the default as the old version 4 is not compatible with the new script used by the app.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I'm talking about the brand new version just uploaded a moment ago
[Android Software/Hacking General [Developers Only]] impactor:
Me too.
[Android Software/Hacking General [Developers Only]] angelgzg:
How to make this script I mount the sd-ext data, my ROM is 4.2 CM 1.10 Lg Optimus One would be very useful
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
In that case i need more to go with, because the issue was fixed on my friends device.

Did you install the new version on the device while you had the issue? Because that will not work. You need to either restore your rom to a working state or do a factory reset
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
What?
[Android Software/Hacking General [Developers Only]] angelgzg:
How to make this script to move data / data to data / sd-ext.?

LG Optimus One CM 10.1
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
By selecting the data option in the app
[Android Software/Hacking General [Developers Only]] impactor:
Yes, I installed it (zip package) over old version.

Do you mean I need to remove it first, and then install it again? That's gonna be a pain cause I will have to get rid of the apps so just want to make sure if this is what you mean.

Actually, the message upon boot seems to be the only manifestation of this problem, so I am not sure if it's even worth bothering with.

By the way - is it worth having journalling on?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The issue I talk about is more than just a message. Its all apps in data that act as they are not installed. If all you get is a message and no other issues, then dont do anything. This is another very monor issue.

Which option are we talking about, just the top main one? And no gray message is provided below the option?
[Android Software/Hacking General [Developers Only]] angelgzg:
It does not just move the applications
[Android Software/Hacking General [Developers Only]] 4D3:
yes, i checked the config pageand it said busy box installed correctly, script missing or incomplete, so i reinstalled the script using the app and i get bootloops.

is there anything i can give you from my device that will help this?

thanks
[Android Software/Hacking General [Developers Only]] kla960:
Thanks. The new version is working on my Desire. Is it possible to add the size of data that will be transfered to ext4 for each option?

It will be very help full to know that.
[Android Software/Hacking General [Developers Only]] MaEdCo:
I installed a new ROM with init.d support, after I installed Mounts2SD, I change the filesytem of sd-ext from ext4 to ext2 which I formated with

now I get a warning after reboot, and the log says Storage threshold not changed. Sqlite3 binary is missing!, I read a previous post a guy with the same problem, so I disable all options (Applications,Data,Dalvik Cache,Cache), still the same warning/error :(, I dont wanna make logs, I already many hours just trying to move the application data to the sd, is really too hard? is really to much too ask? :(

EDIT

I think I fixed it, installing sq3lite, now I get this:

Storage thresold is set to 1%

:(
[Android Software/Hacking General [Developers Only]] gianiaz:
Thank you for your answer.

How much space it needs, and how I can check?

I've opened the terminal emulator and checked with df -h , checked the system partition and it was sayng 250M full, then I have reinstalled blackrose hboot and changed to 260;, now it says the 260M its full. (after a fresh installation).
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
If your ROM is running M2SD in safe-mode, then you will only be able to move applications, not dalvik or data

First tell me where it hangs, before or during the boot animation?

If you get the boot animation, then I would like for you to grab a logcat and also use an adb shell to get the output from "df -h" and "ls -l /data".

I will see if I can get time to add something like that. However, you don't have to worry about moving data of to big a size from one partition to another, the script does match the size of the content with the remaining space on your partition before moving anything

The script is working fine for you. The sqlite binary is only used to change the Android Storage threshold which allows you to install more applications before android alerting you about low storage. And if you install the newest version (1.2.0), it no longer alerts you of the missing sqlite3 binary. However it does not mater to you now as you have already added the missing binary :)

I would do a serious check on the ROM that you are installing. It seams to be using much more space than you have available. There should always be something left on /system after flashing a ROM. However, M2SD does only require a few 100Kb. But that does not even seam to be available to you
[Android Software/Hacking General [Developers Only]] impactor:
Then I won't bother for the moment.

The one in SD-Ext partition section.
[Android Software/Hacking General [Developers Only]] BleedingIris:
Hi.. once again..I was using the script only version and wasn't able to use rmount ,because out of 2GB, I wasn't able to install apps at about 200 MB because of low storage notifications...

Does this mean that this issue is fixed? And I can use the whole 2GB...:eek: if so, can you please tell me, how did you fix it technically (even if I don't understand it)..Is it by modifying settings.db in com.Android... (coz I tried something like that and it didn't work) please:rolleyes:?

Also, can I move to rmount now without issues:eek:?

Please reply..

cm9b11/mcm9b3 htc a310e
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
There are two of them in that section, which one?

However, neither of them are that important. If your sd-ext is mounted and your content is being successfully moved, this could be a small bug in the app's detection part. I will take a look at it and see what could be the reason.

EDIT:

I have looked at the script, and I see one thing that could cause this. In your settings you have either set the journal to enable or disable? If the script is unable to change the current state, but the binary does not return any errors, it just saves the current state to the script configs. When the app then matches the current state against your settings, they will not match and you will get an warning indication.

I will add a message for this situation in the next version, but anyway, your problem is likely that the script was unable to change the state of the journal. To remove the warning, just set the journal to "Automatic" in the configure part.

If you have installed the new M2SD App/Script, then I see no reason why you should not be able to use your sd-ext. Apps should already have been moved by default if you have rebooted your phone and not changed any of the default settings.

M2SD uses more than one technique to fix Android's low storage issue with sd-ext. Changing some app cache permissions, moving the main cache if the internal is to small, moving some app caches and temp folders if the current storage locations is to small and changing the storage threshold in the main database.

Whether or not you can use r-mount depends on your ROM's init.d. If your init.d is executed as a service, than the script will run in safe-mode which will not allow r-mount, data or dalvik-cache.
[Android Software/Hacking General [Developers Only]] impactor:
I can see only one "Ext (3/4) Journal" option.

I asked about journalling without relation to the warning message I am getting. I just want to know if there is any benefit coming from (not)using journalling.

I always had it on Automatic because setting it to ON did return an error which I can actually see in the logs.
[Android Software/Hacking General [Developers Only]] BleedingIris:
No I wasn't using the app.. just the script.. in those days remember...

So this issue is fixed right?

No more 10% right?

cm9b11/mcm9b3 htc a310e

Issue fixed right?

cm9b11/mcm9b3 htc a310e
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Of cause there is. The journal makes frequent writes to the sdcard. And as most know, sdcard's has a limit of how many writes can be made to each block. So by disabling the journal, you will extend the lifespan of your card

You will have to try. The script as it is now, has nothing to do with the old one. It's a completely re-written/new script. I cannot say 100% that it will work for you. All I can say is that it is working for more than 5000 other people, me included. That does provide a great chance that it will for you as well.
[Android Software/Hacking General [Developers Only]] gianiaz:
Came here only to thank you, that was my problem (can't install init.d).

Bye
[Android Software/Hacking General [Developers Only]] crossfire77:
hello i want to install your mounts2sd_ext4_1.2.0.zip on my wildfire s(ICS custom rom) so what i have to do?

like i read that i have to flash it from recovery then its done? or i have to configure this script?

please explain.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You can install from recovery or you can just install the app from market from which you can install the script directly. The app install also works for S-On devices.

Also is wildfire not an MTD device?
[Android Software/Hacking General [Developers Only]] crossfire77:
i have HTC WILDFIRE S (A510e) the next model of wildfire. but i dont know about MTD device.it has low internal memory like after installing rom it has around 100-110 MB space remaining.so is it MTD device? oh it has only 512 MB ROM.

and yeah app works good but it has any configuration? i read your thread,so its bit confusing like what to do.and i ll flash new rom so better i use flashable zip of your script.

so after flashing zip,will i have to do anything ? like downloading app and configure script from it or it ll show me directly space as per my sd-ext partition?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Chech to see if /proc/mtd exists. If not then it is an ext4 device.

You can configure everything from the app. If you flash a new rom without wiping data, then you should install from zip. This will install the script, the app and configure busybox. And your settings are safe as they are saved to the data partition. If you install a new rom WITH full wipe, then it does not mater if you use the zip or just install the app later as you dont have any data left on sd-ext anyways
[Android Software/Hacking General [Developers Only]] TVT73:
Hi Dk_zero-cool,

i am happy about your last update. it solved the dalvic-cahce problem of cm 10 for HTC pico. :good::victory:

The not working new AOPK for pico seems to be a problem of garuda Kernel, others has also problems, and other memory scripts are also not working on this kernel. But i don´t think that is your problem to solve.

On other thing, wich is maybe a missunderstanding about the memory displaying from Android with your app.

I will give you some screenshots where you will see some strange memory sizes. Also have a look at the size of internal memory which is shown by android. Is it normally that there will be only 154mb shown?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Yes this is normal. android cannot see the sd-ext size because Android does not know that it even exist.
[Android Software/Hacking General [Developers Only]] TVT73:
ok good to know. because the original rom without script sees the ext4 and shows internal memory as 1gb.

On picture one you will see a wrong memory size (negativ value). It seems not to make a problem, but i ám not sure.
[Android Software/Hacking General [Developers Only]] crossfire77:
okay thnx for help.i will go with zip.and yeah there is mtd file on my phone.but if i installed ICS or JB rom on my phone.it does support ext4 partition and my sd-ext partition is also ext4.so which zip i should you? the mtd or the ext4?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
MTD or Ext4 has nothing to do with sd-ext or ext4 support. It's decided based on the internal partition types like system and data. You need the correct zip because both device types uses different mount methods in the recovery. You cannot use ext4 on mtd because mounting system and data would fail and no files would be copied to the device.
[Android Software/Hacking General [Developers Only]] crossfire77:
okay go it bro.thanks for it.so i will go for mtd zip.now i think your app is better.just install rom with init.d support and install app..it will configure all itself..:cyclops:
[Android Software/Hacking General [Developers Only]] 4D3:
during

will do asap

sorry for my ignorance, but how to do this?

thanks
[Android Software/Hacking General [Developers Only]] crsklr:
Script isn't working for me. Short story: I suspect it's due to some kind of delayed SD mount. Or maybe fail to mount. I think the cause has something to do with Superuser. This is also the same symptom with any other sdext script.

1. I boot it up

2. Watching logcat on computer with nothing alarming happening.

3. Unlock screen

4. Tons of force close windows (like 50-80 of them)

5. At this time, if I check mounts, sdext is unmounted

6. If I close all forceclose windows, it'll kill the android system somehow and give me the white HTC screen, so there's no way to navigate anywhere.

Posting logcat in a min. Let me generate one.
[Android Software/Hacking General [Developers Only]] crsklr:
Okay, got a boot log (and some interaction postboot). Not a very big one, that's for sure.

So, with this second entry, was m2sd trying to request reboot or something?

I/PackageManager( 2401): Unpacking native libraries for /data/app/com.spazedog.mounts2sd-1.apk
W/PackageManager( 2401): Not granting permission android.permission.REBOOT to package com.spazedog.mounts2sd (protectionLevel=3 flags=0x8be44)
D/HomeLoaders( 2508): Application(40): ApplicationInfo{406825a0 com.spazedog.mounts2sd}
D/HomeLoaders( 2508): Add to appinfoCache ResolveInfo{40682418 com.spazedog.mounts2sd.StatusActivity p=0 o=0 m=0x108000}, icon=0 android.graphics.drawable.BitmapDrawable@406f3648
I/ActivityManager( 2401): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.spazedog.mounts2sd/.StatusActivity } from pid 2508
I/ActivityManager( 2401): Start proc com.spazedog.mounts2sd for activity com.spazedog.mounts2sd/.StatusActivity: pid=2915 uid=10008 gids={1015}
I/ActivityManager( 2401): Displayed com.spazedog.mounts2sd/.StatusActivity: +1s220ms
W/PackageManager( 2401): Not granting permission android.permission.REBOOT to package com.spazedog.mounts2sd (protectionLevel=3 flags=0x8be44)
D/su ( 2938): 10008 com.spazedog.mounts2sd executing 0 /system/bin/sh using shell /system/bin/sh : sh
I/ActivityManager( 2401): Starting activity: Intent { flg=0x10000000 cmp=com.spazedog.mounts2sd/.LogActivity } from pid 2915
I/ActivityManager( 2401): Displayed com.spazedog.mounts2sd/.LogActivity: +370ms
I/ActivityManager( 2401): Starting activity: Intent { flg=0x10000000 cmp=com.spazedog.mounts2sd/.LogActivity } from pid 2915
I/ActivityManager( 2401): Displayed com.spazedog.mounts2sd/.LogActivity: +473ms
I/ActivityManager( 2401): Starting activity: Intent { flg=0x10000000 cmp=com.spazedog.mounts2sd/.ConfigureActivity } from pid 2915
I/ActivityManager( 2401): Displayed com.spazedog.mounts2sd/.ConfigureActivity: +398ms

Update: I just noticed something. If I reboot with the script disabled (safemode), it will show a warning saying "an error/warning was detected". If I view the last log, it shows nothing with a warning on it.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Search google on how to use adb on Windows. I use Linux myself, so cant't help you there

First, safe-mode is not when the script is disabled, it's a state that is active when certain init.d methods is detected.

Second, the important log is the one from the boot, not after the boot.

Just boot your phone with the script enabled and then get the file /props/content.log

This contains the m2sd boot log
[Android Software/Hacking General [Developers Only]] crsklr:
v/Preparing configurations
v/Waiting for sdcard to initiate
v/The sdcard device was located at /dev/block/mmcblk0
v/Setting sdcard readahead to 512Kb
v/Checking sdcard partitions
v/Using /dev/block/mmcblk0p1 as fat32 (sdcard)
v/Using /dev/block/mmcblk0p2 as ext4 (sd-ext)
v/Using /dev/block/mmcblk0p3 as SWAP
v/Running file system check on sd-ext
v/Setting optimized mount parameters on sd-ext
v/The sd-ext partition was mounted successfully at /sd-ext
v/Preparing to move content between /data and /sd-ext
v/Moving content from /data/dalvik-cache to /sd-ext/dalvik-cache
v/Attaching /sd-ext/dalvik-cache to /data/dalvik-cache
v/Optimizing the internal nand partitions
v/Setting optimized mount parameters on system
v/Setting optimized mount parameters on data
v/Setting optimized mount parameters on cache
v/Looking for new system apps in /data/app-system to link to /system/app
v/Activating SWAP partition
v/Setting swappiness value to '0'
v/Preparing to replace the cache partition
v/Unmounting internal cache partition
v/Attaching /sd-ext/cache to /cache

Contents of /props/content.log

I only enabled moving dalvic cache and cache, just so you know.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The script is working fine according to the log. Did you disable safe-mode? Because if your ROM is running the script in safe-mode, then could get problems by disabling it
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It seams that init.d is being executed swice? This would cuase problems.

Also safe-mode has nothing to do with the script being enabled. It should not be disabled unless you know what you are doing.

Try enabling debug in the app settings, reboot and provide the log again. This will give me more info.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
With your current config the sd-ext is mounting fine and everything is as it should be. Your problem might be the partition itself. Try formating it without using CWM Recovery. That one always makes problems
[Android Software/Hacking General [Developers Only]] crsklr:
Can do. Should I format the whole SD card or just the 2nd partition? Is Minipartition okay to use? I'm also familiar with team win's recovery.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Just sd-ext and TWRP is creat, using it myself

EDIT

Also install a different busybox version. I can see from the log that yours have some some limited commands that could give you problems, like FC issues.
[Android Software/Hacking General [Developers Only]] Dovidhalevi:
I am not really interested in all these wild possibilities. In the end, unless on has a huge sd-ext, they are all "robbing Peter to pay Paul."

I am quite interested in the cache handling, however.

/data/data/ holds both non-volatile app data and volatile cache. Getting this all off /data would, with empty caches, gain 30-40meg with all my apps which is certainly nothing to kick about. I tried manually symlinking and got a great bootlock. CM10 ROMs are intolerant of many of these tricks. I wonder how the other scripts play with CM10.

The functionality of mount2sd to symlink volatile caches elsewhere if there is less than 40meg on /data? How might I implement this and I would always want to do it and put this volatile stuff on one of the mostly-unused very roomy tempfs. If it goes away on reboot, saves me the trouble of cache cleaning and this data is no longer available for snoopers.Browsers, Play, Maps, etc., can use large cache files which can reduce /data space to a critical level. Keeping these elsewhere makes sense.
[Android Software/Hacking General [Developers Only]] mixednuts:
In noticed that setting my journal to auto / off I get a general notification of an error, but the debug log itself lists no error.

But, if I set the journal to on I then don't receive any error notifications at all.

Attached my content.log and the debug log both with journal on and auto / off.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Not to sound harsh, but you should read up about volatile and non-volatile. A cache cannot be one or the other. It can however be stored on a volatile storage (Such as RAM, in this case a tmpfs) or non-volatile storage like the Nand Drive (/data or /cache) or the external sdcard (/sd-ext).

In order for this to make sense, A2SD scripts would have to transfer data from one internal partition to another. When you move data away from the internal nand drive to an external source, there is no way you can call that "robbing Peter to pay Paul".

There are a lot of phones in use which have between 128Mb to 500Mb of /data storage. In a time where just a simple browser like Chrome or Firefox uses 50Mb+ (App + Data) of that storage, there is not enough space for a lot of apps. Adding an additional partition between 500Mb to a couple of gigs helps a lot.

The rules have become more strict in Android 4.1+. However you will find these new strict rules have been added to the permission rules. If you get FC, it is most likely due to a folder with wrong ownership or permissions.

You might want to remember that any data placed inside a tmpfs mounted folder, is stored in RAM and will therefore steel memory from your system. So even though they might look roomy from a 'df -h' point of view, they are really depended on how much RAM is in use, and your system will be depended on how little data is stored in your tmpfs.

There is a reason why this is not the first option used by M2SD

Also note that Android automatically empties the main /cache partition on each boot. The only cache folders that remains after boot, are the apps own cache folders stored in /data/data/*
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Ignorer it. It is a small bug in the App caused by the app comparing your current state "1=enabled or 0=disabled" with your settings "2=auto". It should ignorer this check whenever it is set to auto. Will be fixed in next release.
[Android Software/Hacking General [Developers Only]] mixednuts:
My apologies... just tested it with journalling actually set to off: no error at all. Thanks so much for all your help and hard work!
[Android Software/Hacking General [Developers Only]] mixednuts:
Should I be concerned if I receive the following message now and then:

"Error detected while checking sd-ext. Auto correction was performed!"
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
No, as it states, auto correction was performed. It's because Android does not always do a proper unmount of sd-ext on shutdown