Database Info

[Q] ext2/ext3/ex4 and lynux-swap with incubus RLS14/15

Hi, I have been testing several NAND set-ups
-system to NAND and data to resized data,img
-system to resized system.img and data to resized data.img
-system to NAND and data to ext2
...
I am currently using NAND and data to ext2 partition, so all apps are installed there. After lots of reading I can not understand posts that are obsolete and posts that are not so I would appreciate if someone can explain me the basics and optimal setup for incubus superfroyo RLS14/15 roms:
I have now 4 partitions:
1) fat32,
2) 1,5G ext2 (app, app-private etc),
3) 1,5G ext2 (lost+found folder) and
4) 96M lynux-swap.
- How can I turn ext2 to ext3? do I need to do so? I have also read about ext4. Upgrading to ext3/ext4 applies to my 2) partition, to my 3) partition or to both? will I loose data stored? "there is no ext3/ext4 fs because there isn't the support on the compiled kernel. Ext3/ex4 are journal file system so are bad for limited writing device like nand or sd and thre is no good rease to use it" answered by l1qd1.
- How can I check if my lynux-swap is enabled and used by the rom?
- Do partitions 2) and 3) really need to be <1,5 G? why so?
- Can I take apk from apps folder in partition 2) in case I want to keep them for future fresh installs?
- What is lynux-swap optimal size? a 1,5G partition would be worse than 96 M? Why?
- Which tools are you using with incubus roms to manage installaion location and similar functionalities?
Another big mark I have is about deoxeding installed aps (not belonging to the ROM). Should I do it? why? how?
Pretty basic stuff I guess for experienced users & programmers, but I am new to lynux and android. Have read lots of things but it is difficult to learn by myself what would work with our Polaris and incubus ROMS and dzo/kk kernels,

Stick to ext2 man, you won't turn your old engine to 240mph on a Ford Model T.
You're not getting some major boost if the hardware dosn't use it, so I'd stick with ext2.
And you also want Super FroYo on your ext2 partition, yes? I'm here to help.

- How can I check if my lynux-swap is enabled and used by the rom?
adb shell
Code:
free
if on swap you have 0 it isn't enabled.
Code:
swapon /dev/device
to enable it or i suggest you tu use compcache.
- Do partitions 2) and 3) really need to be <1,5 G? No
- Can I take apk from apps folder in partition 2) in case I want to keep them for future fresh installs? Yes but not all apk support this
- What is lynux-swap optimal size? a 1,5G partition would be worse than 96 M? Why? Too Big = more sparse but it's a problem only for real disk so you can create a swap big as you want but it's unuseful (100 M is enaught)
i suggest you to switch to my kernels because are more updated and kk move to another device.

Yah l1q1d I love ur kernels. Eager for more !

l1q1d, I am testing your kernel as you advised me. I could apply the wifi patch without problems using your androiupdate18-09-10, as you told me some time ago they are both 2.6.25.
However I do not manage to turn linux-swap on: that's what I do: I install ubuntu, I use G-Parted to create partitions on the sd card. When I do so, the third partition is always shown as linux-swap in G-Parted but when I test adb shell -> parted -> print, it always shows as ext2. I can not dismount and can not swap on it.
The other way round, if I deleted all partitions with G-Parted and create the partitions with mkpartsfs or if I use mkfs to change the third partition from ext2 to linux-swap, then sometimes I can swap on it (directly on adb shell or with G-Parted) but when I unplug the device will tell me the card is empty and will not be able to mount it, access it from ubuntu or from the device. If I reboot then, the system will hang until I install both data and sysetm to nand. This happens no matter if I activate or not from the polaris or even if I switch on or off usb mode. The card at that point is useless. I guess the partition table or some other basic file is messed.
Could you please explain a little more how can I come with a 13.5G fat32 partition, a 2,4 ext2 partiions and a 0,1 lynux swap swapped on partition??
I really need to test this set up, since with the standard set-up (system to nand, fat32 for files and ext2 for installed apps I can not install all apps I use since performance drops significantly).
regards

well, ... dumb me, maybe with compcache you are referring to launch a script?
where do I get this compcache.sh? how do I launch it? from adb? from the terminal? from the sd card?...

[Utility] ext4 data2sd for Froyo ROMs

If you are always low on program memory, this data2sd might be for you. It works with any Froyo for the G3.
Note: This won't wipe your data, but you should have a backup, just in case. First backup the phone to the SD card, then the SD card to your computer. Be cautious. I give no guarantee whatsoever. If your phone behaves funny, even eats your cat afterwards, I take no responsibility.
Note: starting with version 3, the new storage size will NOT be reflected in the Task Manager or in Titanium Backup. I'll see what I can do about it.
You need a rooted phone and an SD card, preferably 2 GB or more and class 6 or better (higher). data2sd doesn't make your phone faster. Much to the contrary: it extends your memory at the cost of speed. That said, if your SD card is of a class smaller than 6, this will work too. The slowdown, however, will be noticeable in some situations.
Three steps are needed. First, we need a kernel with built-in ext4 if you don't have one. Second, we bring the data2sd into its place. And third, we create an ext 4 partition with the desired size. Now follows a detailed description of these steps.
Step 1: Check your kernel
You need a kernel with built-in ext4 capability. The custom ROMs mostly have one. If you are running a stock kernel, you must install one, e.g. from http://forum.xda-developers.com/showthread.php?t=978823 . Follow the installation steps detailed there. (Changing the kernel does not wipe your phone).
Step 2: Install data2sd
You now must install data2sd onto your phone. As long as you didn't modify your SD card (as long as partition #2 is not ext4), this will have no further impact on your phone.
Download data2sd.zip from below and unzip it. There's a single file in there: data2sd.sh. Use the tool that suits you best to transfer it to the SD card of your phone. With adb, you would do
Code:
adb push data2sd.sh /mnt/sdcard
Now either start a terminal emulator with a root shell or use adb again. With adb, you would execute
Code:
adb shell
Make sure you are root (the prompt reads '#'), else run "su". Now type in:
Code:
# sh /mnt/sdcard/data2sd.sh
You will see some lines about what is happening and a final confirmation.
That's it. Again, your phone will continue to behave as usual.
Step 3: Prepare your SD card
You can use any amount of program memory up to the size of your SD card, but be sure to leave some room for application data on the normal (#1, vfat) partition. As a rule of thumb, 0.5 GB of program memory will satisfy most needs, 1 GB is plenty.
If you're running Linux, prepare a second partition (must be partition #2) with the desired size. Use the usual utilities to do so. This includes gparted, but there are also other means. If you use gparted, you can follow the description for Parted Magic below.
If you have no access to a Linux computer, even not your friend's, your (probably) best choice is to run Parted Magic from a live CD. For this, go to http://partedmagic.com, and burn your CD. Instructions on how to do it with different burning tools are also there.
Step 3.1: Partition and format your SD card with Parted Magic (also applies to gparted)
The following describes the steps to partition your SD card with Parted Magic. You don't need to use this method - use the tool that suits you best.
I assume you have gparted or Parted Magic running and your SD card inserted into the card reader of your PC. Now select your card from the drop-down menu of available drives in the upper right corner. You better double check that you're on the correct drive (card). It will happily erase your system disk if told to do so.
Right click near top into the block designating your current partition #1. Select "resize". (I assume that your partition #1 is the only one. If not, delete the other partition(s)). Change the size to the total size of your SD card minus the desired size for program storage (/data). Confirm your selection.
There is now a gray block designating free space to the right of your first partition. Right click it and select "New". In the following window, leave the sizes as they are. Leave "create as" to be a primary partition, and change "file system" to ext4. Confirm your selection ("Add").
The gray block at the right has changed to a colored frame. Right click it again and select "Format as". Select "ext4".
If everything went well, you can now click on the green check mark in the icon bar near the top, confirm, and watch Parted Magic resizing your normal (#1, VFAT) partition and creating the new ext4 one.
4. Finale furioso
Now insert the SD card and reboot your phone. The Task Manager will report the new size in its rightmost tab, as do the other utilities like Titanium. All user apps and data should be in place. All will look like you have soldered in an extra chunk of internal memory. Despite not being directly visible, your program memory is resized to be the new partition. You see its size and its usage (in percent) by running
Code:
df
from adb or from a terminal emulator. Have a look at the subdirectories of /data displayed there.
As a final step, you can safely remove data2sd.sh from your SD card (/sdcard). It is not needed any more.
Q&A
* How can I remove my SD card while the phone is on?
You can't. Don't try. Always switch your phone off before you remove the SD card.​* How can I return to the state before data2sd?
Remove the SD card. All user data and apps will be there in the state you left them before you installed data2sd. The data2sd script you have installed simply does nothing as long as there is no ext4 #2 SD partition.
If you want to reuse the SD card, remove partition #2. This can be done with each partitioning tool, you don't need Linux.​• What about app2sd from Kyrillos 3.0? Is it compatible?
Yes. But "no" for the "no wipe" version which was offered for a short period of time. In the latter case, clear out the ext4 partition (important: do not forget the hidden .data2sd_initialized file) or simply reformat it before reusing it.​* It doesn't work. What can I do to help diagnose the problem?
See if the file /mnt/asec/data2sd/log.txt exists. If it does, have a look at it and try to make sense of it. If it doesn't tell you anything useful, add it to your error description in the forum here. If there is none, mention that in the description.​* What things must be considered if I flash a new ROM?
As always with such actions, make sure you have a backup. That said, just flash the new ROM and then install data2sd. When you reboot with the SD card in place, all user Apps and all data should be there. No restore from backup required.
Only in the rare case that the new ROM explicitly requires you to NOT restore your old data, e.g., from Titanium, you should reformat your ext4 partition (to clear it out) and proceed as advised by the ROM makers.​Versions:
2011-03-19 Initial release
2011-03-21 Version 2
- Updated for ROMs without /system/etc/init.d
- Simplified installation of the core parts
2011-03-23 Version 3
- Vibration bug fixed
- App2SD mode added: If the ext4 partition bears the volume label "app2sd" on a new blank SD, only /data/app is moved. This greatly reduces size benefits, but results in nearly no speed loss.
- Just run the data2sd.sh file (as described in step 2) to upgrade without data loss.
- Note: the actual size will NOT be reflected as described in the Task Manager or in Titanium.

Gosh this sounds so complex and risky! Isn't there a easier way?
☞★sent from my Galaxy3!!
♪drajax!! ♬♂ツ

drajax said:
Gosh this sounds so complex and risky! Isn't there a easier way?
☞★sent from my Galaxy3!!
♪drajax!! ♬♂ツ
Click to expand...
Click to collapse
Flash Kyrillos' v3.1 where's the script's allready built in...

It is less complex than it sounds. The description is just really very detailed. The details may sound confusing until you try it. And if you have access to Linux, it is really simple. We Linux users also have to use a different operating system when we flash our phones.
Alternative: Install Kyrillos 3.1. It contains the same data2sd and comes with a partitioning tool. But, as far as I can tell, you need to reformat the SD card's vfat part on the phone and lose the data there (not sure, however).

when i try to set permissions it says permission denied . Any help?

http://www.appbrain.com/app/move2sd-enabler-(root-only)/com.leinardi.setinstalllocation

Just one quick question....
I am having the stock JPM ROM... in that case do i need to have some new Kernel to use your data2sd???

I'll be using this!
Sent from my ACID Lestatious v1.4.5.5 Galaxy 3 FROYO

When i write down "/ # cd /system/etc/init.d/"
it says "sh: cd: can't cd /system/etc/init.d/"
What am i doing wrong???

Pinak.ahuja said:
when i try to set permissions it says permission denied . Any help?
Click to expand...
Click to collapse
You're not in a root shell. Enter "su" as your first command.

next2devil said:
When i write down "/ # cd /system/etc/init.d/"
it says "sh: cd: can't cd /system/etc/init.d/"
What am i doing wrong???
Click to expand...
Click to collapse
Don't know. Try this:
cd /system
cd etc
cd init.d
and report where it fails and if you are using adb or a terminal emulator. If it doesn't fail, continue with the line after the cd command.

Awesome work mizch!

We can refer to below link for partitioning of sd card to ext4 using adb
http://forum.xda-developers.com/showthread.php?t=534714

Hi Mizch,
Thanks for the script. have few questions; requesting for an answer:
1. Once data2sd is done, will sd card be auto mounted on reboot?
2. I am running JPM with Apollo's data2sd (ext2 partition for apps 1.1GB). What will be the benefit of ext4 over ext2?
3. I understand that i have to remove apollo's lagfix and then apply ext4 data2sd. Is there a way, i can also apply lagfix?
Thanks

jaskiratsingh said:
Hi Mizch,
Thanks for the script. have few questions; requesting for an answer:
1. Once data2sd is done, will sd card be auto mounted on reboot?
Click to expand...
Click to collapse
Yes. And for the first boot, it gets initialized too.
2. I am running JPM with Apollo's data2sd (ext2 partition for apps 1.1GB). What will be the benefit of ext4 over ext2?
Click to expand...
Click to collapse
Reliability, especially in crash cases and generally when the phone is shut down without a clean unmount. Ext 4, being a journaling file system, tries to keep the file system in a consistent state whenever possible. ext2 does nothing like that. So, when you forcible switch off your phone by long pressing the power button, most likely you are continuing with a damaged file system whose errors accumulate from now on and will eventually become visible at some time later.
There's one drawback, however: ext4 has to write more data than ext2. ext4 must always write the information needed to reconstruct a consistent file system to its journal.
3. I understand that i have to remove apollo's lagfix and then apply ext4 data2sd. Is there a way, i can also apply lagfix?
Click to expand...
Click to collapse
If I'm correct, the lagfix converts /data (your program storage) to ext2. Since /data is now handled by data2sd and converted to eyt4 anyway, you cannot use lagfix any more. You need to remove it.

mizch said:
If I'm correct, the lagfix converts /data (your program storage) to ext2. Since /data is now handled by data2sd and converted to eyt4 anyway, you cannot use lagfix any more. You need to remove it.
Click to expand...
Click to collapse
Thanks for the quick reply mizch. If i have to check apart from data, if anything else is converted into ext2, how can i do that?

jaskiratsingh said:
Thanks for the quick reply mizch. If i have to check apart from data, if anything else is converted into ext2, how can i do that?
Click to expand...
Click to collapse
have a look at the output of 'mount' or 'busybox mount'.

rm 02-app2sd for who use kyrillos ROM...i didn't do that command..but it seems works fine...what does it change if i use that command???

mizch said:
Don't know. Try this:
cd /system
cd etc
cd init.d
and report where it fails and if you are using adb or a terminal emulator. If it doesn't fail, continue with the line after the cd command.
Click to expand...
Click to collapse
I tried what you mentioned.... but again it shows the same error. It works well till "cd etc". Then, for init.d it shows out the error.
It seems the location for init.d is different in my device

next2devil said:
I tried what you mentioned.... but again it shows the same error. It works well till "cd etc". Then, for init.d it shows out the error.
It seems the location for init.d is different in my device
Click to expand...
Click to collapse
Yes. Probably there is none. What ROM are you using? Is it a Froyo ROM and from where?

[Q] Multi-Booting

Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's

Good question ..............i think there is no answer for this question

rvd_516 said:
Hi,
It just came into my mind. Since we can have custom recovery and android recovery also boots, can we have multi boot option in Defy as like in a PC's
Click to expand...
Click to collapse
some resources would have to be used by both ROMs..
with the current hacks it can't be done easily.
i guess some way of ramdisking the shared resources will have to be used.
basically, if you think about a hack for defy ask first:
can it be done in a completely open (=bootloader not locked) phone like nexus ?
if yes, ask:
is it WORKING?
if yes also, so maybe it can be done.
nevertheless, it's easy enough to create a script to backup & restore NANDROIDS.
but then every switch between roms will take like 25+ minutes, so it won't be a real multiboot.

Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.

ephumuris said:
Somebody at one point on the desire was working on something like this. Run rom from nand and other rom from sdcard.
Ephumuris.
Click to expand...
Click to collapse
I think there are two possibilities for this to happen: first of all, we should try NAND boot for the primary ROM, and try somehow to load the secondary ROM from the internal memory (it'll be faster than the SD Card, I think). The problem here would be allowing the bootloader to read from internal memory instead of NAND. I know this can be done based on the number of WinMo-Android and iOS-Android dual boot solutions, with a menu to choose which system to load, in the boot screen.
The second option is the method used by Wing Linux to run Android on old WinMo devices. In this method, you MUST boot in WinMo (or, in our case, in the primary ROM), then open the app that loads Android (the secondary ROM, for us). Android does NOT run emulated in this method, but, since the device can't dual boot directly, the app sends a signal for the device to restart running from the bootloader to the SD Card (for us, internal memory). This second option is, somehow, like the System Recovery app (not 2ndInit), that has an option that reboots directly into Recovery. So, if we can tell the phone to load from custom Recovery (which is, in fact, in internal memory, not in NAND), I think it's possible to make it load an entire ROM from the internal memory (without having to mount it everytime and waiting for the dalvik-cache to load).
However, it's surely a hard work to do.

Yes one from nand and one from sd card..........good......can we partition nand and use it both on the nand itself??

it should really work if we use virtual images or sdcard-partitions instead of system, data and cache partitions.
This can be changed in the init.rc-file(of 2nd-init).
The creator of the 2nd-init-bootmenu should implement this feature.

it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings

Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
Did you try it?

Epsylon3 said:
it is possible... just need 2 new partitions ext3 on sdcard for data and system...
you can use 2nd-boot profile in bootmenu to change dev block links and customize mount settings
Click to expand...
Click to collapse
even i like to know tht did u tried tht?

I managed to boot from virtual system,data and cache partitions with the 2nd-boot-option of bootmenu like ep3 said.
It was a bit difficult because android-init remounts /dev so the changes will be lost but now I found a way.
And: I got recovery working for the virtual system so you don't need to prepare your images, BUT: only the wipe and restore are working. "install zip" will still affect your real system.
My scripts need some testing but after that I will release a first version.

the multboot works for me i writed a cutsom boot sh and init.rc and woila WORKS!
NOT PUBLUC because it not works for all rom
---------- Post added at 04:59 PM ---------- Previous post was at 04:36 PM ----------
this is a dualboot rom
http://forum.xda-developers.com/showthread.php?t=1225179

So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.

I uploaded a new version of my multiboot-script(v0.2)
changelog:
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
Download:
http://www.multiupload.com/UT0TLPR3ZW

m11kkaa said:
So here is the first (very early) version of 2nd-boot:
http://www.multiupload.com/Z17M0WO3SU
Before continuing please make a backup of your phone!
Installation:
Just install it via CWM.
This will place the script in your 2nd-boot and replace the "CWM-Lastest"-script so it will install into the images. BUt can still use the "CWM-Stable" option for your normal system.
I've created 3 empty 300MB ext3-images for system,data and cache so you don't have todo that. Download them here:
http://www.multiupload.com/VY3U4IXRO1
Just copy the folder "fsimages" to your sdcard.
Usage:
After installing the update-zip and copying the files to the sdcard you can reboot into bootmenu, select "Lastest Recovery" and Restore an backup.
Please DO NOT install a ROM with a zip-file. Currently this will affect your real system.
After you restored your backup into the virtual file-system you can boot them with the 2nd-boot-option in bootmenu.
I successfully installed CM7.1 and MIUI-Pikachu-Edition in the virtual filesystem.
Click to expand...
Click to collapse
Thanks for your work.
Did the 2nd android system boots from sdcard?

Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.

m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
Ask pedrodh http://forum.xda-developers.com/member.php?u=2098689
He can help.

Nice work, thanks i will add this soon, in the future bootmenu versions

m11kkaa said:
Yes, but it's very flexible. By changing 2 lines you can let it boot from whereever you want.
I prefer storing it at the data-partition because it's over 1gb in size and my apps are using 200mb only.
I'm looking forward to better bootmenu-integration and boot-image-selection but for that I have to figure out how to compile bootmenu.
Click to expand...
Click to collapse
I released a dual boot version that uses 2nd-boot a few months back, hadn't have much time to improve it since.
I was using loop-back mount with /system and bind mount with /data since it's much more space efficient than just use an ext3 image.

Awesome job. I think u shud create a new thread for it. Dual booting cm7 and miui :O
Sent from my Moto Defy

[DualBoot][Tools][Guide]Essentials v2.1 for Berni's method

As of 28/12/2013, I no longer have this phone. My threads will stay open for all who want to assist others. I've had a great time being a member of the O3D community, so thank you all!
For questions, requests or any other remarks, please don't send me PM, I will not answer. Instead, please post properly in the thread, so that anybody can read and benefit or even assist.
02/07/2013:New version 2.1 (fixed compatibility issues with Gingerbread present in v2.0). Switch_ROM in v2 is now a single script. All other scripts integrated into a "Recovery" equivalent. Fixed bug in wipes. Renamed "bin" folder to "img" (seemed more appropriate). Old v1.0 users must delete their existing DualBoot folder. Don't forget to backup your boot1.img and boot2.img from the old "bin" folder.
Our top developer, Berni987654321, developed a method to dual-boot our phones (follow the link to his page and press his "Thanks" button, he deserves it)! Thanks to him we can preserve our stock ROM with full 3D support and at the same time try out modern Jellybean ROMs like CM10, PACman, perhaps even KitKat some day!
However, dual booters were facing two problems:
1. Switching ROMs was cumbersome and time consuming since it required to reboot into recovery, flash a kernel and reboot again to the other ROM.
2. Recovery only backs up and restores the primary ROM. If someone wanted to try out different secondary ROMs, he would have to set them up from scratch every time.
3. Factory Reset and wipes don't work for secondary ROM in Recovery
This is where I've come in. I have written scripts that fill in these gaps.
Download and unzip the file attached and copy the DualBoot folder anywhere in your phone. It is necessary that all files are kept inside the folder and that the path (all directory names) to this folder contains no spaces.
Usage instructions are on the second post.
In order to keep SMS and Call Logs synchronized between the two ROMs, I use SMS Backup +. Naturally, it needs to be installed in both, primary and secondary ROMs.
You can't install just any kernel for your secondary ROM. You can only use one from Berni's page. Still, you can overclock using CM10 modules by Iodak.
Ilie321 and Defcomg have made a working FM radio app for ICS and JB. Attached at the end of this post there is a modified flashable zip that installs the radio straight into a secondary CM10 ROM. Use it after every Nightly upgrade.
For a long time I've wanted to integrate a "Fix Permissions" option into the Dual Boot Tools script but never found the time. Here you can find a wonderful script and run it with Script Manager after your secondary ROM has booted.
!! 3D support for CM10 !!
We may not be able to view in 3D, but we can shoot!
Defcomg has successfully ported ArcCamera to CM10 / 10.1 based ROMs, fixing at the same time orientation problems for all 3rd party cameras (e.g. Instagram). Attached you will find ARC+V30B_LIBS_CM10+_DualBoot.zip which is modified to flash directly to the secondary ROM. You need to flash it after every Nightly upgrade.
Hit Defcomg's "Thanks" button (Original thread)!
Stock ICS v30a Kernel:
If you have already updated your primary ROM to P920 ICS v28b or v30a, you will need the attached "Kernel-ICS-v30a.zip". Download and copy it to your phone. Follow instructions in 2nd post.
IMPORTANT: Official P920 ICS has locked bootloaders, so before you can boot into CM10 you also have to flash Wkpark's v1.25a bootloaders. OS_Hacking's Tool is an easy way to do that.
New CM10.1 Kernel
With the old CM10.1 Kernel, Bluetooth doesn't work. Attached you will find a new BT-fixed 10.1 kernel modified for Dual-Boot!
ADB driver not installing when in recovery!
It has been reported that after installing ICS on the phone, the computer cannot install the ADB driver when phone is in recovery mode, although ADB works normally when in USB Debugging mode.
Solution:
1. Open Device Manager and connect phone in recovery.
2. Right-click on LGE COSMO USB Device (in Other Devices) and select "Update driver software"
3. Select "Browse my computer for driver software"
4. Select "Let me pick from a list..."
5. Select "ADB Interface"
6. Select "Android Platform Sooner Single ADB Interface" and hit "Next"
7. Say "Yes" to the warning and wait for the driver to install
8. You may have to reboot the computer

Instructions on setting up the ROMs:
In this guide, I will concentrate on how to setup your EXTERNAL SD, because the latest CM10 and CM10.1 kernels modified by Berni expect to find partitions there!
First of all, you need to have ADB installed on your PC and CWM (or other recovery) on your phone. You also need to have unlocked bootloader if you are running ICS. There are other threads that explain how to do all that.
1. BACKUP your EXTERNAL SD card. IT WILL BE ERASED!
2. Download the primary and secondary ROMs of your choice
3. Do the necessary modifications to the secondary ROM as instructed by Berni (Do NOT use Windows Notepad for this. It corrupts the script. Download and use Notepad++ instead).
4. Download the kernels that match your ROMs (as described in Berni's guide).
5. Copy all to your INTERNAL SD (as I said, the external sd will be erased).
6. Boot into recovery, connect to PC via ADB and prepare partitions as instructed by Berni (this is when your card loses all data).
... Detailed Setup Instructions:
Some people reported trouble when trying to partition external SD cards larger than 8GB. So, I rewrote Berni's guide and added a little trick to help.
Follow this guide to partition your EXTERNAL SD card:
1. Turn off your phone. Keep Vol- 3D and Power keys until the LG logo shows. Release all keys. Wait a few sec.
2. You are now in Recovery. Connect your phone to PC with a USB cable, press Windows Start Menu, type:
cmd
Click to expand...
Click to collapse
and hit enter.
3. In the new window that has opened type:
adb shell
cd /dev/block
parted mmcblk1
print
Click to expand...
Click to collapse
For a 32 GB card, you'll get something like this:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 [b]1049kB 31.4GB[/b] 31.4GB primary fat32 lba
Write down the Start and End numbers
For cards larger than 8GB, the End Number is shown in GB. Multiply it by 1000 to cnvert it to MB (31400MB in our example). Make sure you use values in MB and NOT in GB in the commands below.
4. Type
rm 1
mkpartfs primary fat32 1049kB 29400MB ///!!! Instead of 1049kB, type the Start number you wrote down. Instead of 29400, type your End number minus 2000MB !!!
mkpartfs primary ext2 29400MB 30100MB ///!!! Instead of 29400, type the end of your 1st partition. Instead of 30100, type the end of 1st partition plus 700MB !!!
mkpartfs primary ext2 30100MB 31300MB ///!!! Instead of 30100, type the end of your 2nd partition. Instead of 31300, type the end of 2nd partition plus 1200MB !!!
Click to expand...
Click to collapse
At this point, because not all cards have exactly the same capacity, you need to know exactly how much space you have left. Type:
print free
Click to expand...
Click to collapse
You get somehing like:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
32.3kB 1049kB 1016kB Free Space
1 1049kB 29.4GB 29.4GB primary fat32 lba
2 29.4GB 30.1GB 700MB primary ext2
3 30.1GB 31.3GB 1200MB primary ext2
31.3GB 31.4GB [b]87.7MB[/b] Free Space
Note the size of your last free space (87.7MB here). Anything larger than 67.1MB will be sufficient.
Type:
mkpartfs primary ext2 31300MB 31387.7MB ///!!! 31300MB is the end of 3rd partition. 31387.7MB is the end of 3rd partition plus the remaining free space !!!
print
Click to expand...
Click to collapse
this time you get:
Code:
Model: SD 00000 (sd/mmc)
Disk /dev/block/mmcblk1: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 29.4GB 29.4GB primary fat32 lba
2 29.4GB 30.1GB 700MB primary ext2
3 30.1GB 31.3GB 1200MB primary ext2
4 31.3GB 31.4GB 90MB primary ext2
5. Turn off your phone and boot again into recovery.
Type:
adb shell
cd /dev/block
mke2fs -T ext3 mmcblk1p2
mke2fs -T ext3 mmcblk1p3
mke2fs -T ext3 mmcblk1p4
Click to expand...
Click to collapse
Your new partitions are now ready!
7. Flash the ROMs (you may want to keep your original ROM and flash only the secondary one)
8. Flash your primary kernel and reboot to system.
Rebooting will now load your primary ROM.
Partitioning the easy way!
Instead of step 6, you may put your microSD card to your PC using a Card-Reader. Then you may use MiniTool, EaseUS or other freeware partitioning tool to create your partitions. Shrink your main partition and make three new PRIMARY EXT3 partitions AFTER your main one. The 1st (system2) must be 700MB. The second (data2) at least 1GB (you can make it larger if you like to install lots of apps)! The 3rd one (cache2) should be around 100MB. So, do the math and make sure you have shrunk your fat32 partition according to your needs first. After you're done, eject your card from the PC, put it in your phone and continue to step 7.
Important: If for your own reasons you need to create more than the 4 primary partitions mentioned above, then you must convert your card to GPT (GNU Partitioning Table). Minitool has that option. This is because the default MBR (Master Boot Record) partitioning does not support more than 4 primary partitions on the same medium. This is also how the internal memory of our phones is divided into a large number of partitions (P920: 15, SU760: 17) and they are all primary.
New: Easiest partitioning ever!
A new app, AParted, has appeared on PlayStore. You can use it to create both MBR type (up to 4 primary) and GPT type (up to 128 primary) partitions.
Instructions on ROM switching:
1. Go to Play Store and install SManager
2. Download the attachment from 1st post, unzip it and place the DualBoot folder on your phone (anywhere you like)
3. Unzip your primary kernel, place boot.img into your DualBoot/img folder and rename it to boot1.img
4. Do the same for your secondary kernel, but rename it to boot2.img
5. Run SManager, browse to your DualBoot folder and select "Switch_ROM".
6. Mark favourite and su options and run the script.
Your phone will now reboot to your secondary ROM. Use the same script to go back to your primary ROM.
7 (optional). SManager has a homescreen widget system. It lets you add buttons in your homescreens that will directly run the linked script (it has to be put in favourites first).
Alternatively, you may download Flashify from Play Store and flash your desired Kernel.img from there. The advantage is that you may keep and test different kernels for the same ROM without having to rename them or put them in the IMG folder (less initial setup). The disadvantage is that it requires more clicks to switch every time.
Instructions on Backup/Recovery/Wipe:
These scripts work for EXTERNAL SD ROM installations!
1. For full functionality, you must be on PRIMARY ROM (you can't expect to wipe or restore a running system)!
2. Make sure you have at least 2GB free space on your external SD if you want to make a backup.
3. Inside your DualBoot folder there is a script: "Recovery_Tools". Run the script with SManager (make sure you have the SU and Wlck buttons pressed). For Wlck to work, you must first enable it from SManager settings.
4. You will now enter the Dual Boot Recovery Tools. There are several options. Type the number you want and press enter. All functions are pretty self-explanatory.
It's very important to know that every backup overwrites the previous! The backup is kept in /sdcard/_ExternalSD/ROMs/rom2_backup. If you want to keep more than one backups, you can always rename the folder, but remember to change the name back if you want to restore your ROM.
The "Advanced" option takes you to the "Wipes" menu. For a Factory Reset, you must wipe Data2 and Cache2. For a Full Format, in order to clean-install a new ROM, you may also wipe System2.
Remove Dual Boot - Regain card space:
This is pretty simple:
1. Backup the contents of your SD card.
2. Boot to your primary ROM
3. Go to System Settings/Storage and select Erase SD card.
Case scenario / Easy migration to dual boot:
Say you have already installed CM10 in a single boot setup but you miss the 3D features and you want to restore your good old gingerbread backup or flash the new P920 ICS, but keep your CM10 setup as a secondary ROM in dual boot.
1. Make sure you have at least 4GB free in your external SD.
2. While still in CM10, use SManager to browse to your DualBoot folder, run the "Recovery_Tools" script and select option to "Backup/Migrate ROM1".
(Go fry some bananas cause this will take around 6-7min!)
3. Now backup your external SD to your PC and reboot to recovery.
4. Follow the guide to partition your external SD.
5. Restore your Gingerbread or P920-ICS backup or flash your favorite ROM and reboot into it.
6. Restore your external SD backup from PC.
7. Run the "Recovery_Tools" again and use the "Restore ROM2" option.
(Eat your fried bananas cause this will take another 6-7 min!)
Your original CM10 installation is now relocated to external SD as your secondary ROM. Use my instructions on ROM switching to boot into it.

Wow man, this is awesome!
I'm bussy right now but I'll try it out as soon as i can.
Thanx thanx thanx thanx......

this is awesome!!thank you so much for this...one of the reasons i don't use dual booting is that the switching process is not efficient
and now its much better..so thank you again

Re: [DualBoot][Tools]Essential tools for Berni's method
Great job mate, you just made my life a lot easyer.
Thanks
Sent from my LG-P920 using xda app-developers app

Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Some people experienced trouble partitioning external cards larger than 8GB. Specifically, the 4th partition (cache) wouldn't fit. So, I rewrote Berni's guide on partitioning, adding one extra trick to do the job without problems!
Sent from my 3D phone

Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Added a way to migrate your single boot CM10 installation to dual boot without losing your settings!
Sent from my 3D phone

dreccon said:
Added a way to migrate your single boot CM10 installation to dual boot without losing your settings!
Sent from my 3D phone
Click to expand...
Click to collapse
Thank you. You are awesome

Very good bro, just find a way to put script shortcut in powermenu, that would be real cool. I think it can be done by editing android.policy.jar

Re: [DualBoot][Tools][Guide]Essentials for Berni's method
Added support for the new P920 ICS v28b.
Sent from my 3D phone

It just occured to me that there is yet another way to easily switch ROMs without using my scripts! Whoever is interested may try it.
This method is ideal for those who use Xbsall's prerooted v28b. That rom comes with milaq' 2nd init recovery which lives in the system partition. The recovery partition remains with stock recovery which is practically useless. So, 1st of all make sure you have wkpark's v1.25a bootloader (a prerequisite to boot into both ICS and CM10). Then flash the secondary boot.img into the recovery partition. This way every "normal reboot" will take you to your primary ROM and every "reboot to recovery" (or pressing vol-down at bootup) will take you to the secondary ROM. To go to milaq's recovery you would press vol-down at normal bootup while keys are flashing or run the dedicated app from android. So, there you have it: a fully functional dual-boot android. Ofcourse, this can apply to any ROM that can be fitted with 2nd init recovery.
Any questions?

dreccon said:
Added support for the new P920 ICS v28b.
Sent from my 3D phone
Click to expand...
Click to collapse
yaaaa great man i love it :good::good::good::good:

Hey dreccon , say that i want to keep cm10 as my primary ROM and v28b as my secondary , if you can also include those steps in your main post i'd really appreciate it.
Thank you for this great contribution.

Re: [DualBoot][Tools][Guide]Essentials for Berni's method
boltthrower56 said:
Hey dreccon , say that i want to keep cm10 as my primary ROM and v28b as my secondary , if you can also include those steps in your main post i'd really appreciate it.
Thank you for this great contribution.
Click to expand...
Click to collapse
Sorry, can't do that! It's not that it can't be done, but you would need a v28b kernel modified to look for the system partitions in the SD card. I don't know how to do this. Berni does! That's why all the modified kernels are on his page and not here!
What you can do right now is to migrate your existing CM10 to the card. I've written instructions on 1st post.
Sent from my dual-booting ICS/JB O3D!

dreccon said:
Sorry, can't do that! It's not that it can't be done, but you would need a v28b kernel modified to look for the system partitions in the SD card. I don't know how to do this. Berni does! That's why all the modified kernels are on his page and not here!
What you can do right now is to migrate your existing CM10 to the card. I've written instructions on 1st post.
Sent from my dual-booting ICS/JB O3D!
Click to expand...
Click to collapse
Allright , thanks anyway...
I'll pm bernie and ask about modifying the kernel.
I already did a little research about it , i think i can do it easily , i just need someone to point me out to the right direction.

Thank you very much for the Scripts they work really good and fast...:good:

ADB can not get started with the recovery, I tested with CMW and TRWP (terminal), any ideas?

infernum said:
ADB can not get started with the recovery, I tested with CMW and TRWP (terminal), any ideas?
Click to expand...
Click to collapse
Are you using ICS as your primary ROM? It seems that there is a driver problem in ICS. I'm using v28b and my computer can't install drivers when I connect phone in recovery, although everything works perfect when it's booted in Android. All I can tell you is to try updated drivers (the link has been posted in v30a thread. If it still doesn't work, you'll have to use TWRP console instead of ADB. If this is your case you'll need further instructions cause the commands in TWRP console are a little different than ADB.
Sent from my dual-booting ICS/JB O3D!

Also, see if updating Android SDK makes any difference.
Sent from my dual-booting ICS/JB O3D!

dreccon said:
Are you using ICS as your primary ROM? It seems that there is a driver problem in ICS. I'm using v28b and my computer can't install drivers when I connect phone in recovery, although everything works perfect when it's booted in Android. All I can tell you is to try updated drivers (the link has been posted in v30a thread. If it still doesn't work, you'll have to use TWRP console instead of ADB. If this is your case you'll need further instructions cause the commands in TWRP console are a little different than ADB.
Sent from my dual-booting ICS/JB O3D!
Click to expand...
Click to collapse
I can get into adb from fastboot , recovery and debugging with defcomg super light ROM ?
Sent from my LG-P920 using xda premium

[MOD][2016-11-01][V3.01]TURBO DATA - Get an 8GB Data-Partition ...

TURBO DATA - Get an 8GB Data-Partition!​
Use SD-EXT as new Data partition​
presented by​
~~~~~~~~ delta-roh ~~~~~~~~ ​
HIT THANKS for delta-roh (1st post) ​And, please, don't forget to Rate this Thread - thank you!​
You love your Sensation, but:
The 1 GB of the data partition limits you?
You don't like Link2SD?
You don't want to use the to SDCard feature?
You don't want to use data2sd or similar scripts?
You are afraid of broken links?
Then this is the Turbo for your HTC Sensation​
Features of TURBO DATA
Version 3.01 (release date 01st Nov 2016)
new corrected error in cpio to support 2nd level subdirectories
new Mod for Ivanich CM11 to get Data on SD-Ext, but have Dalvik internally (FAST!!!) - refer to Post 2
Version 3.00 (release date 29th Mar 2015)
new now my Delta-Roh cpio.bat is integrated
new Delta-Roh cpio without cygwin! - all tools integrated als always
new No need of Windows 8.1 administrative rights (as for cygwin)!
new Now manual changes can be done to all scripts of the ramdisk
new Very easy handling!
new This version now also supports ViperS-Roms!
new If you like, you can download only the Delta-Roh cpio package (see below)
Version 2.02 (release date 02nd Mar 2015)
new now also handles .img (boot-Image files)
new added loop for performing patterns more flexible
new added patch check - exit if no pattern was found
new added ramdisk size check
Version 1.04 (release date 21st Feb 2015)
First Version by delta-roh
new handles normal flashable zip, that include a boot.img
new works fully automatically
new support of command line call
new Drag+Drop support
new A lot of checks to make the procedure safe
new Writes a logfile parallel to the screen output
new Does not change your original zip
new the resulting zip can be flashed directly
Click to expand...
Click to collapse
Idea:
Our beloved Sensation comes only with 1 GB of available internal memory and that is too less to work, even if you don't install a lot of games. When I tried several thinks (app2sd, app2sd-ext, Link2SD etc.) I recognized, that modern SD-Cards are very fast and our Sennsation has got a very good interface to suppport high speeds. Even better, the SD-Cards of SanDisk (SanDisk Extreme Pro, SanDisk Extreme Plus and SanDisk Extreme) are even faster, than the internal memory. Therefore I got the idea, to make a seperate external SD partition (SD-Ext) to the new Data partition. It works flawlessly and fast. But how does it work? The first step of the Android startup process is to mount the boot image and to mount a ramdisk, that is part of the boot image. In this ramdisk you will find the mount table for the primary partitions - it is called fstab.pyramid. Here you will find, that the data partition is mounted to /dev/block/platform/msm_sdcc.1/by-name/userdata or to /dev/block/mmcblk0p23. The only thing to do is, to change this to /dev/block/mmcblk1p2, which is the second partition of the SD-Card.
The attached ZIP now contains a Batch file together with all necessary tools to do this job for you completely automatically. It extracts the boot.img file from your flashable zip, extracts the kernel and the ramdisk.gz, unpacks the ramdisk, patches the fstab.pyramid as described above, repacks the ramdisk, repacks the boot.img, makes a copy of the original flashable zip, exchanges the boot.img in this new zip - done! You have got a new flashable zip, that will mount the second SD-Card partition as your new data partition. I do this with an 8 GB sd-ext partition and therefore now have got a Sensation with 8 GB of available internal memory - no need to care about memory or tools like Link2SD any longer!
Click to expand...
Click to collapse
Installation:
Take these steps:
the attached zip contains the batch and all needed utilities
extract the directory tree in the zip to a location on your Windows harddisk
place your flashable zip or boot-Image in the main directory which also contains this batch
open a cmd-windows by clicking "Start here.bat"
call "MakeNewImage" with your flashable zip or boot-Image: MakeNewImage <your-rom-or-image.zip>
or
just Drag+Drop your flashable zip or boot-Image to MakeNewImage.bat
after processing you will find the new flashable zip or boot-Image in the subdir "new"
all original parts (boot.img, kernel, ramdisk(.gz)) are in the subdir "original"
all new parts (boot.img, kernel, ramdisk(.gz) and your new flashable zip) will be in the subdir "new"
if you call the batch another time (or Drag&Drop a new image to MakeNewImage.bat, the complete subdirs will be deleted before processing the new fashable zip; the batch will then create the directories again with the new parts
if you like, you can make additional changes to the fstab.pyramid or init.rc ...
Click to expand...
Click to collapse
YOU MUST READ THIS OR YOU WILL BRICK YOUR DEVICE:
You have to know this - read carefully:
Tested with a lot of CM11 and CM12 Roms
It will only work for fashable zips that contain a boot.img, like @SultanXDA CM11, @ivanich CM12, @shantur CM12 - it will NOT work e.g. for @mike1986 Android Revolution, as this does not contain a boot.img.
ViperS 5.2.1 / Viper 5.3.0 do not work at the moment.
You should only make your sd-ext to the new /data partition if you have got a highspeed sd-card e.g. SanDisk Extreme-series; otherwise it will work, but your Sensation will slow down.
You need a sd-ext partition on your sd-card as second (!) partition (/dev/block/mmcblk1p2); create it within the recovery or use e.g. MiniTool Partition Wizzard and create a first partition as primary fat-formated and a second partition as primary ext4 formated. IF YOU HAVE NOT A SECOND PARTITION, YOUR DEVICE WILL NOT BOOT!
This is ONLY for the HTC Sensation/XE; it can work also for flashable images of other devices, but then you have to make your changes to fstab and/or init.rc manually!
After flashing the new image the /data partition will be created on the second SD-Card partition (sd-ext).
After booting for the first time you can restore a backup by using e.g. Titanium.
If you want to look at /data within the recovery you have to mount sd-ext and then flash the Aroma Filemanager; there you can see the complete data partition by browsing to sd-ext.
You can make a nandroid backup within the recovery. Note, that the sd-ext tar file is your (new) data partition.
If you want to go back, then just flash a nandroid of a former backup or flash a not patched zip and make a clean installation.
If your rom thread provides a seperate zip for the kernel, then have a look at the provided zip! If it contains a boot.img, then it has to be patched at first by using MakeNewImage.bat in the same way as with a complete rom. If the kernel zip does not contain a boot.img but only the kernel, then you can flash it directly.
If you want to wipe Dalvik-Cache you can't do it with the "wipe Dalvik"-command in Recovery; instead go into Recovery, mount sd-ext, flash the Aroma Filemanager or use the TWRP-Filemanager, navigate to the directory sd-ext (your new /data) and delete the directory dalvik-cache.
You can not restore a data partition from a former installation to sd-ext, because the tar file also stores the partition name and, therefore, does not restore a data file to the sd-ext partition, even it you rename the backup file. As said before: Make a clean installation and then restore via e.g. Titanium.
Click to expand...
Click to collapse
Thanks:
Special thanks to:
carliv (http://forum.xda-developers.com/member.php?u=5186178)
for mkbootimg.exe (https://github.com/bgcngm/mtk-tools)
GnuWin32 (http://gnuwin32.sourceforge.net/packages.html)
for sed.exe and grep.exe (libiconv2.dll, libintl3.dll, pcre3.dll, regex2.dll)
Igor Pavlov (http://www.7-zip.de/)
for 7z.exe and 7z.dll
Karl M. Syring (http://unxutils.sourceforge.net/)
for dd.exe, gzip.exe, od.exe, printf.exe, rm.exe, sha1sum.exe, tee.exe
@danishaznita for testing the first version
Click to expand...
Click to collapse
USE IT AT YOUR OWN RISK - NO SUPPORT! READ SECTION 'MUST READ' ABOVE CAREFULLY!​
DOWNLOAD TURBO DATA MOD V3.01​
DOWNLOAD Delta-Roh cpio Package V1.51 (already integrated in Turbo Data Mod)​
If you like my work, press​
THANKS for delta-roh ​
And, please, don't forget to rate this thread - thank you!​
If you want to use my work, please don't ask for permission, but leave my headers in my files, make a reference to me in your thread and respect the other persons in the thanks section, if you use their tools.​
copyright by delta-roh 2016

Reserved
Mod for Delta-Roh MakeNewImage-V3.01
EXPLICITLY for Ivanich CM11 ONLY!!!
This mod mounts a sd-ext partition to /data and leaves the dalvik-cache on the internal
memory. Therefore you will get e.g. an 4 GByte (depends ob your sd-ext partition size) data
partition and the original 1.1 GByte internal memory as additional and fast memory for
the dalvik cache. This is the fastest way regarding the porformance of the Sensation.
Installation:
- Download and extract "Delta-Roh MakeNewImage"
- start "MakeNewImage.bat" with "cm-11-20160810-UNOFFICIAL-pyramid.zip"
- answer the question "Do you want to auto-patch fstab [y/n]" with "n" (no) - don't close the command box!
- an explorer will open in the subdir of the new ramdisk, now do the following mods:
--- override the existing "init.rc" with the new one from this zip (Download below)
--- override the existing "fstab.pyramid" with the new one from this zip (Download below)
--- create a new directory "data0" in addition to the already existing data directory
--- copy/paste (press Ctrl-C then Ctrl-V) the file "data.attrib"
--- rename the new file ("data - Copy.attrib" or named similar) to "data0.attrib"
--- now you can close the Explorer and answer the question "Manual changes finished [y/n]" with "y" (yes)
Now you will get a "sdext_cm-11-20160810-UNOFFICIAL-pyramid.zip" that can be flashed.
NOTE: You will need a sd-ext partition on your sd-card.
DOWNLOAD Ivanich CM11 DATA MOD​

I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?

hinxnz said:
I think this a great idea, many thanks. I've been wanted to do it the since you mentioned the other day, I wanted a new phone too xD Well I did it today and then just seen your post. I did it on PC though (Linux) and mounted userdata as dalvik-cache so easy to wipe and maybe quicker loading (in theory). I may have mounted it differently to you (see screenshot), and are your attributes/flags the same?
Click to expand...
Click to collapse
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?

delta-roh said:
My Turbo Data mounts sd-ext to data (same to you) but don't mounts the old data to the dalvik-cache, because I have a SanDisk Extreme Plus and it is faster than the internal memory xD
BTW, my batch works completely with Windows and even without cygwin. At the moment I am working at a cpio batch that works with Windows without elevated rights and without cygwin as well...... xD
Question: what did you do to mount dalvik-cache to the original data partition? And which Filesystem manager did you use in the screen shots?
Click to expand...
Click to collapse
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Edit: Just checked my SDcard and it older than yours and probably not as quick but mines a 32Gb SanDisk Ultra SDHC-I and works fast enough for now.

hinxnz said:
Yeah I must have the same SDcard as you by the sounds of it xD have so for ages and probably the reason I've been using Mounts2SD for so long but yeah got sick of it not working as expected as CM12/Android 5.x matures. Thanks to your idea/earlier post though and a bit of mucking around with it as I did have a few hiccups, eg. offset ramdisk address, all went well in the end and is quite a simple process once the know how. Over the time of using M2SD I felt like write speeds were slower (not actually tested but just how it felt) hence the reason why I use the f2fs file system on the sd-ext and I didn't want to leave my internal data partition all alone and unused. I was deciding and still am really for what to use it for, first ideas was for private storage or for app data but then I thought Dalvik-cache could be good because wiping it would be easier without modifying recovery or applying a script. I did this all on native linux (ubuntu) with a few binaries added, I was thinking of making a flashable zip to do the whole process if possible and I think it is but would be a bit of experimenting process and don't really have the time as yet and also you have got this underway already, so I probably wont. I don't mind posting the binaries I used and what I did if it will help, maybe you'd be into creating a version that doesn’t require a PC. The file manager I'm using is FX File Explorer (pro), I only just switched to it, well bout a month ago and I find it a good alternative to ES or Root explorer, it also has the material design theme which goes nicely with CM12 and has 90% of all the necessary features I need. I mounted internal data with fstab which I've attached for you and I've linked the /data/dalvik-cache/arm directory to it. You can name the internal data partition to whatever you like too.
This also could be good for those that corrupted their data partition too that was caused by the twrp recovery version from their site (not ivanich's version).
This is also good because I don't have to link things like Googles Drive cache to sd-ext anymore, for example it caches a copy into data say from a ROM downloaded with it.
Click to expand...
Click to collapse
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?

delta-roh said:
You mounted userdata to /dalvik-cache and I suppose you then changed the init.rc to link the dalvik-cache to /dalvik-cache - right?
Click to expand...
Click to collapse
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /dalvik-cache/arm /data/dalvik-cache/arm

hinxnz said:
Yes that is correct.
Code:
# symlink dalvik-cache to internal location
symlink /data/dalvik-cache/arm /dalvik-cache/arm
Click to expand...
Click to collapse
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache

delta-roh said:
Why not this way?
Code:
symlink /data/dalvik-cache /dalvik-cache
Click to expand...
Click to collapse
I did it this way because in the past, I've had issues with linking dalvik-cache to other locations due to SELinux but only on later versions of Android 5.x though.
But then again I haven't tried this approach with this configuration yet.

thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?

phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2

phan_tom said:
thanks delta roh..
so, at least how much R/W speed that need run this?
based on Sandisk Extreme spec, min speed is around 60MB/s for read. is it correct?
Click to expand...
Click to collapse
The internal memory (original /data) has got about 30 MB/s read and about 15 MB/s write speed. The card has to match these values. But the speed declarations of the cards are allways higher, than they are in real life! A SanDisk Extreme matches these speeds in real live. The Extreme Plus and Pro are better and will give you REAL FUN!
Just try it - to have a Senni with e.g. 8GB internal memory is awesome!

danishaznita said:
Sandisk Extreme is the highest u can go , i think any Class 10 sdcard can handle this , but with a little lower speed
Sent from my Note 2
Click to expand...
Click to collapse
Right! Having 8GB of internal memory and no mem-problems any more is also worth a little bit less speed (in the case you got no SanDisk Extreme). BTW: Thank you for testing the pre-releases and did you try the release 1.04?

Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!

ChimeyJimmey said:
Unfortunately,
Your method does NOT suits me fine - extremely laggy and slow.
I have tried it with the latest ivanich CM11 and CM12 builds.
I have preliminary made an 8Gb ext4 partition on my 32GB class 10 MicroSD card.
I always set governor to intellidemand, clock to 1242MHz and use cfq for I/O.
Will test Links2SD method now.
Nevertheless,
keep up the good work!
Click to expand...
Click to collapse
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.

delta-roh said:
I tried the CM12 build of ivanich and it has got an extrem low performance of the runtime environment (in Antutu 77 compared to Sultans CM11 with 900) and I tested it with dalvik-cache in the data partition and not on sdext. It seems as if the runtime system was compiled with debug options.
Click to expand...
Click to collapse
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.

Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny

cutejerk420 said:
Will it work on viper sense5.0 and what if my mcard crashes because sometimes it stops working and I have to format my mcard. So what if it crashes will it affect my senny
Click to expand...
Click to collapse
Nobody is able to answer these questions. Normally SD-Cards are absolutely stable. Make a regular nandroid backup e.g. every day.

hinxnz said:
Huh I just downloaded Antutu from playstore to test myself, still on the same configuration and my score is way higher than you got on CM12 and even higher than your CM11 score, only ran the benchmark once so it not like the highest out of several either on stock frequency, governor, scheduler etc.
Click to expand...
Click to collapse
Remarkable! Please post your configuration - do you use F2FS and on which partitions?

delta-roh said:
Remarkable! Please post your configuration - do you use F2FS and on which partitions?
Click to expand...
Click to collapse
I use f2fs on sd-ext and ext4 on userdata, I use the fstab which I posted earlier and added the symlink to init.rc, on line 319 to be exact xD
Unpacking, repacking and making boot image was done on Linux, not sure if that would make a difference though.