yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The script does a hell of a lot more than just mounting a few folders. It is not intended to be executed from the recovery, and would not work there.

The Recovery and Android it self, is two different OS'es, and doing a full backup of an OS while you are booted into it, is simply wrong. Backing up your applications and their data is fine, and there is plenty of automated applications that can do that for you. But recovery backups should only be made from within the recovery, by the recovery.

Otherwise you should, as I said, write to the developer of your backup tool. I am not the creator of that one and will not spend time adding support hacks for other software which should contain the support itself. The creator could implement a check which determines the mount point of the data sub folders and add the backup for either data or sd-ext depending on these mount points (Otherwise sd-ext backup support from a booted OS is useless). Then you would be able to restore the content to the correct partitions from within the recovery. But again, not my software, so it is not my place to make those changes.
[Android Software/Hacking General [Developers Only]] demoncamber:
Can someone tell me what's the advantages/disadvantage of using this app with a second fat-32 partition as opposed to an ext4?

And how exactly to do it? Is it just as easy as following the partition instructions for ext-4 but making it fat32?

Thanks! PM or directly quote me so I know you replied to me!
[Android Software/Hacking General [Developers Only]] mixednuts:
Won't work with fat32... only EXT.
[Android Software/Hacking General [Developers Only]] demoncamber:
beta it is! Love your work man!
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
If you create the sd-ext as fat32, it will be able to mount it and all that, but you will get problems. Fat32 file systems cannot use the Linux permission schema, which means that you cannot give folders and files the correct user and group permissions. Android demands this on the data partition, as this is used to secure files and folders from being read and written by the wrong processes. If Android cannot use these permission schemas, it will properly not boot your device if you place /data content in it.

So if you do this, don't move any apps or app data to sd-ext. Also, why would you do this? Fat32 is an outdated limited file system that should have been removed from IT years ago. The only reason it still exists, is for compatibility reasons with different platforms and systems, but this is soon to be replaced by exFat.

Did it work?
[Android Software/Hacking General [Developers Only]] demoncamber:
It did work. Long story short, it was the 32gb sd card I got off ebay, it would format fine but was giving me issues after partitioning it, eventually I found out through an RMA from A-Data the card was counterfeit!

So both the beta and older version of M2SD works fine, when I put in my old 8gb card, it was the SD card's fault.
[Android Software/Hacking General [Developers Only]] TopperBG:
Is that so named Procedure to remove Link2SD and/or migrate to Mount2SD ?
[Android Software/Hacking General [Developers Only]] gu5t3r:
http://xdaforums.com/showpost.php?p=38722147&postcount=1527

This is the way that worked for me without losing any app... After installing M2SD script select to move dalvik and apps and reboot to CWM and use adb or AromaFM console and paste commands in order...

If

for sym in `ls /data/app/`; do if [ -L /data/app/$sym ]; then rm /data/app/$sym; fi ; done
mv /data/app/* /sd-ext/app/

won't work for removing symlinked apps you can try

for sym in /data/app/*.apk; do if [ -L /data/app/$sym ]; then rm /data/app/$sym; fi ; done
mv /data/app/* /sd-ext/app/
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Use the Beta version. It will take care of Link2sd for you when you install the script.
[Android Software/Hacking General [Developers Only]] TopperBG:
Thank you !
[Android Software/Hacking General [Developers Only]] TopperBG:
Do I must to uninstall Link2SD after first start of Mount2SD Beta and collecting data phase ?

Edit1: A lot of apps missing, actually don't know moved or linked, but will restore nandroid backup and will check again. Will report later.

Edit2: Problem apps are linked. Now I'll try to move it on SD with Link2SD in bunch. But few thoughts - some apps not works like that, for exmpl this one with widgets? How to proceed? [MENTION=3147360]dk_zero-cool[/MENTION] mentioned apps could be moved in /system/app - is that will resolve unworking widgets?

Edit3: I haven't got a luck with migration :(

Will follow [MENTION=4665716]gu5t3r[/MENTION] guide to manual move it...but in my device folders are slight different, IDK why.

So:

1.Install M2SD, install script, setup to move app and dalvik-cache, reboot to CWM

2.adb shell, used two diff command from gu5t3r

3.after type mv command....

Any help will be appreciated

Few more steps:

1.Remount /sd-ext

2.Made /sd-ext/app (there is no such folder)

3.Moved all /data/app/*.apk
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You should be able to just install the Mounts2SD app. Then when you go to the app settings and install the script, it will auto remove any pre-existing sd-ext script, including all Link2SD injections, Link2SD application etc.

When you reboot, Mounts2SD will remove links from /data/app, move any applications left in /data/app to /sd-ext/app and attach the whole /sd-ext/app folder to /data/app.

If this does not work accordingly, Link2SD stores applications in other locations than /sd-ext/app? If this is the case, I would like to know.
[Android Software/Hacking General [Developers Only]] TopperBG:
I'm pretty that Link2SD stores apps in /data/sdext2

And here is df:

/dev/block/mmcblk0p2 1.8G 384.9M 1.3G 22% /data/sdext2
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
That is just a mount point. As long as the apps is placed within an 'app' sub-folder, they are placed correctly. Said in another way, (/dev/block/mmcblk0p2)/app/
[Android Software/Hacking General [Developers Only]] TopperBG:
So the goal of migration must be accomplished only with install of M2SD script ?

But that way won't work for me :(

Will play with manual commands like gu5t3rs to see what happens.

Edit: Is it there and if it is, where are stored log file of script ?
[Android Software/Hacking General [Developers Only]] gu5t3r:
Link2SD stores *.apk in root of /sd-ext, not in /sd-ext/app....

Probably that is the problem when moving from L2SD to M2SD...

I moved all manually and it worked...

---------- Post added at 04:08 PM ---------- Previous post was at 04:02 PM ----------

Did you execute all commands from the LINK or just 2 from post?

---------- Post added at 04:14 PM ---------- Previous post was at 04:08 PM ----------

Also if you're using non-beta version, after installing M2SD and configuring you need to remove link2sd and it's script in init.d and /system/etc/install-recovery.sh

From your answer I think you didn't ran all commands from link... (just 2 from latest post)

Try also preemptive disabling of safe-mode... (I couldn't move dalvik with safemode on)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well then, there is the issue. The Beta version removes everything Link2SD related like init.d script, it's parts in recovery-install (Or whatever it was called) and the app itself. So all I need added in Mounts2SD, is having APK's moved from the root of sd-ext into app/ on sd-ext. Will have that added before releasing it.

Is APK's the only thing moved to the root of sd-ext? What about app data, app-asec, dalvik-cache and so on?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Based on what I've just learned about Link2SD, you install my app, then use that to install the script (This will remove everything from Link2SD) and then reboot into recovery and type in the fallowing commands in an ADB shell

mount sd-ext
mkdir /sd-ext/app
chown 1000.1000 /sd-ext/app
chmod 0771 /sd-ext/app
mv /sd-ext/*.apk /sd-ext/app/
[Android Software/Hacking General [Developers Only]] gu5t3r:
Yes, only *.apk are in root of /sd-ext; dex and lib files use proper path...
[Android Software/Hacking General [Developers Only]] TopperBG:
Thanks guys, will try it immediately.

Yes Gu5t3r I know your great post how you convert L2SD>M2SD from a long time. This is how I've know about M2SD in facts :)

But after your post yesterday decide, that dk_zero-cool made most of the things except move /sd-ext/app/*.apk. And you know about this in beta.

So we've learned a lot of this posts !

Oh, one more important thing - usually users setup L2SD to install new apps on external partition! Due to this M2SD also is installed on the SD card....could this be a problem too.
[Android Software/Hacking General [Developers Only]] gu5t3r:
[MENTION=3147360]dk_zero-cool[/MENTION] Are there big improvements (speed? boot time?) in v6 beta compared to stable version 5.5?

Is it worth updating or to wait final version?

I'm using 5.5 and it works great, never had any problems (except I need to have safe mode off for dalvik to be on sd-ext)...

(and init.d method is properly implemented, used your injector as guide=)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Everything is improved, speed (As much as possible), different Device/ROM/Shell support, features, stability, fail-safes for not to mention application layout. Both script and application have been rewritten from scratch.

There is still a few minor things to work out, and still some things missing. But even in this state, it runs better and with fewer issues than 2.x (Script 5.x).

Here is a list of flaws in the current beta

Lack of support in RootFW for the new SuperUser Daemon

Has been fixed, just not uploaded yet.

This issue will also be in current Play Store Release

Lack of support for ROM's placing system files (Not just apps) in /data/[name]_s/

Support has been added, just not uploaded yet

This is also an issue with current Play Store Release

Missing onBoot receiver for auto pre-configuration to avoid long loading on first launch and alert about errors or warning.

This is still on the doto list

A small issue in the scripts environment setup which only affects a few stock ROM's (Only one occurrence)

Has been fixed, just not uploaded yet.

Missing in-app notification when log contains warnings or errors

This is still on the doto list

Move APK's from the root of /sd-ext into /sd-ext/app when removing Link2SD

This is still on the doto list

So the the whole thing is more or less done. Enough people have been given feedback from various ROM's and devices, which tells me that most issues has been resolved. What I am actually working on getting done before the rest of the small stuff, is some code cleanup and the new RootFW3 which I would like to have added before releasing this as final.
[Android Software/Hacking General [Developers Only]] TopperBG:
Few things I observe in Beta:

1.Can't disable Safe mode

2.Can't mark libraries to be moved to sd-ext

3.Can't mark System content to be moved

4.Even typed Driver ext3 as FS of sd-ext, it's shown on main screen as ext4 and File system check disabled

5.The log is empty always, but Debug is enabled.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Your init.d does not support safe-mode as you don't have a service implemented version. It's not used on your device, so no need to be able to disable it.

Your not running Android 4.2+ which has /data/app-lib

You don't have any system content in /data

You select your type in config, the app displays the driver used to handle it, it even says DRIVER in the headline (Some kernel does not include Ext2 an Ext3 drivers, as the Ext4 driver is backward compatible and fixes some bugs that affect all 3 types)

Okay, this is an actual bug. Check to see if the file /tmp/log.txt exists and if there is any content in it.

Please note that Mounts2SD implements different features based on what your Android version, available binaries and so on. Disabled features means no support. This can either be because of the Android version (Like Android below 4.2 not using /data/app-lib or pre 4.1 not using app-asec), it can be lack of kernel support (Like SWAP or ZRAM), it can be missing binaries (Like File System check which needs e2fsck) or just the fact that it is not needed (Safe-mode or System Application which does not need to be enabled if you don't have any).

Disabling a View, like checkbox etc. in Android is something that you need to implement. I don't implement bugs on purpose, so if something is disabled, it's most likely because it should be :)
[Android Software/Hacking General [Developers Only]] :
will this work with other init.d scripts/mods also? Becuase I have Pure Performance X Mods
[Android Software/Hacking General [Developers Only]] TopperBG:
Yeah, now it's clear !

I love this intelligent way of setup options .... but we don't used to use such options till now ;)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Don't know what that is. Only conflict would be other sd-ext scripts.
[Android Software/Hacking General [Developers Only]] gu5t3r:
In latest LuPuS kernels I followed your example (init.d injector); /system/etc/init.d are run with exec and /system/etc/boot.d scripts are run as background service from init.rc

I have 5.5 version and when I enable safe mode I can't move dalvik... Is that fixed in v6 as safe-mode can't be disabled on exec init.d implementation...

Didn't test beta, will wait for final...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
If it detects Android services during script execution, safe-mode options will be available, even if you have an exec implementation which does not stall services which it seams that you do. I have had one such issue before. Think it's the ROM's init that has been altered to work differently, don't know why. Never the less, it's not a bug in the script.
[Android Software/Hacking General [Developers Only]] TopperBG:
Dalvik is moved. Safe mod as I said cant be on/off even.

In status page I see green dot against Dalvik cache and 205Mb data.

Strange, against Data I see 235Mb but the dot is gray ?

Swap is enabled but not function (0.0b from 244Mb dedicated partiotion)

ZRAM works - 47Mb of 64Mb.

/tmp/log.txt is missing at all.

And one bad thing (for me) - Album is FC, ver.5.0.A.0.6. It's a system app, is it moved to sd-ext or .... ?

In that way, could be good idea to make some tool or option to move apps from app to app-system folder ;)
[Android Software/Hacking General [Developers Only]] gu5t3r:
I don't mind having it enabled... Once I selected to move app and dalvik I never touched the configuration again... It works perfect...

I odexed with dexopt-wrapper most of my system apps so its dalvik is on system partition for speed...

And /cache partition is left unused as downloads are moved on sd-ext so i'm using /cache for swap...

Works perfect for my LT18i...

M2SD is a life savior for me, my CWM backup has 2GB (only 250MB of that is rom) XD

ROM is Sony ICS 4.1.B.1.13 Stock

When you release v6 final I will report if I still need safe-mode off...

---------- Post added at 11:28 PM ---------- Previous post was at 11:19 PM ----------

Nice, maybe I 2 wont need to turn safe mode off...

Swaps have priorities, if zRam is in front of Swap, Swap won't be used until zRam is full... Think there's no point in having zRam and swap, as when zRam is full system will use only swap until it's full, so after zRam is filled it's same as you have only swap, except zRam is eating your ram...

Lupus kernel removes /tmp on successful boot...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Data is gray, because it is placed on /data and not /sd-ext, hence the option is disabled. But that does not mean that you don't have any data, so why would it not say 235Mb if you have this amount of data in /data/data? Should it only display the size of the folder if it is placed on sd-ext? If so, how would you know how much data you would move if you enabled the option? Each content option is related to one or more folders on /data. Each of these folders get's their size calculated, regardless whether the option is enabled or disabled. Gray means that the size is used on /data and green means that it is used on /sd-ext.

And SWAP Usage of 0b does not mean that it does not work. It just means that nothing is swapped on it, which makes sense since you have plenty left on your ZRAM partition, which have first priority as RAM is faster than your sdcard. You will properly never see the SWAP being used with 64mb ZRAM. I have never had Android SWAP above 50MB, even with swappiness set to aggressive.

If it is placed on /data/app-system and you enabled the apps option, then yes. Place it in /data/app_s instead. That uses the System Files option so you can move regular apps to sd-ext while keeping system apps on /data. You can do this with anything from /system, like /data/lib_s, /data/framework_s etc.

I have thought about it. But that will be as an update at a later time after I release it. It's not something you just add. I also have to handle app updates etc.
[Android Software/Hacking General [Developers Only]] TopperBG:
Yeah I catch the point of Zram and SWAP....

But I fill more and more difficulties.

Viber was reset and deleted history - ok, never mind.

FB and FB Messanger was unregistered, ok small problem.

FB in Xperia™ can't be setup (and it was setup before migration)

I think from here comes the problem with Album, because it sync FB and Picasa albums.

Gu5t3r how you advice - to disable SWAP in M2SD and use you swap2cahce script in init.d ?
[Android Software/Hacking General [Developers Only]] acestars:
Since i used beta version every boot will bootloop for sometime maybe for 4 or 5 times. Its not happens when use version 2.

I can disabled safe mode and my config now are move app and data.

Sent from my Z71
[Android Software/Hacking General [Developers Only]] gu5t3r:
I use only swap on cache; 64 MB (CM roms recommend 18% or ram which is 64MB on 355MB of ram); I disabled M2SD to mount 3rd mSD partition

My theory is that when I moved app and dalvik to /sd-ext all load is on mSD... So, swapping to unused /cache partition lifts some load from mSD...

Test one day swap to mSD, test swap2cache another (but with zRam disabled)...

Swapping to mSD without /sd-ext is ok, but /sd-ext + swap is overload on mSD IMO...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Strange. Boot loops normally do not resolve them self like that. Can you grab a logcat of this?
[Android Software/Hacking General [Developers Only]] :
Alright, thanks!

BTW Pure Performance X
[Android Software/Hacking General [Developers Only]] gu5t3r:
It's better that you don't know....

PPX is crap load of crap overlapping crap scripts...

When sane person opens PPX flashable zip first reaction can only be WTF?

Look at the M2SD and V6_SC source code and then look in PPX code to see how NOT to write tweak scripts...
[Android Software/Hacking General [Developers Only]] acestars:
here is the logcat. i modified some of your script such as rename app-system to system-app and add system-lib for link to system/lib.
[Android Software/Hacking General [Developers Only]] :
Now that I did look in the zip, so I see. But Seems like a good plan when you look at the thread.

So what tweaks do you recommend?
[Android Software/Hacking General [Developers Only]] TopperBG:
After made successfully migration of apps I've choose to use swap2cache because cache is almost free. Will test few days.

But I feel lag, it's not from swap (i've used this way before). Some apps FC, other stop responding. Will try to get logcat in this moments.

This night the device reboot at least one time... will keep on eye what's will happens today.
[Android Software/Hacking General [Developers Only]] PerfectSlayer:
[MENTION=3147360]dk_zero-cool[/MENTION] Let me know when you want I start translation for 3.x branch ;)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well you can start already. There is only missing one String for the in-app log notification. Can add this when I get home from work to complete the string file. And this time I have added all strings to one single file, so you don't have to look trough multiple files this time.
[Android Software/Hacking General [Developers Only]] Daniel D.:
[MENTION=4665716]gu5t3r[/MENTION] & [MENTION=3147360]dk_zero-cool[/MENTION]

Inspired by your discussions on the last pages, I've to throw in some questions.

I setup Lupus v16_R1 with SmartassH3 & sio and V6 SuperCharger with 2048 KB sd-card read cache.

After starting M2SD v6-b3 for the first time, the status page displayed (without touching the settings!) 4 KB/2048 KB as the internal/external MMC readahead cache and sio as both scheduler. After entering the settings, creating just the boot script and rebooting the phone the status page shows cfg as scheduler and 128 KB as external readahead cache (WTF!?).

Ok, setting sio as both schedulers and 2048 KB as external MMC cache all things are fine for me again - but do these options affect V6 SuperCharger or the kernel settings? They're confusing me everytime and why do they change after creating the boot script for the first time?

The option File System Check is activated and deacitvatable, but it's stated as "Disabled" in the status page!? edit: Ok, my fault, I need another binary. What about greying this option out if the binary isn't available?

Since using my phone I ask myself why I need the cache partition? It's always empty (got a record of 2 MB in the last weeks) and I read about the Swap2Cache script. Is it this one?

So the best configuration for my phone would be:

- Lupus Kernel v16_R1

- M2SD with moved applications (does data brings any advance in speed?)

- Swap2Cache script in init.d (without .sh extension?)

A last question: Does the option "Settings Style" has any function? If yes, which one? The description isn't that clear.

Thanks for your time!

P.S.: Please send me the string file. I'll try the german translation.
[Android Software/Hacking General [Developers Only]] gu5t3r:
Dunno if its app error or you have some other scripts in init.d that modify readahead_kb cache

I use THIS modified (by me) version of swap2cache...

---------- Post added at 11:14 AM ---------- Previous post was at 11:12 AM ----------

You can name it 50swap2cache for example... You can use any number after M2SD....
[Android Software/Hacking General [Developers Only]] Daniel D.:
I don't use any other crappy init.d! :rolleyes: :D
[Android Software/Hacking General [Developers Only]] PerfectSlayer:
Ok, so I will have a look at the end of the week to update french translation.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Mounts2sd is made to change a lot of things that you can configure in the app. If SC v6 is run before mounts2sd during boot, then yes, it will affect some of v6's settings.

Also the beta app should already disable file system check if e2fsck is missing.

And Settings Style makes everything look like the app settings page, it's under the theme section and states "use settings style globally". That description sais plenty i think. Just try it. You can uncheck if you don't like. Just remember to restart the app as android can't change themes other ways. Just hit back until it closes, that will completly exit the app.
[Android Software/Hacking General [Developers Only]] Daniel D.:
I asked because I didn't see any changes after enabling the style option and restarting the app. :o
[Android Software/Hacking General [Developers Only]] Nightshadow931:
Will M2SD remove int2ext4+ and work properly if I just install it over int2ext4+ ?