Related
unCoRrUpTeD Dual Boot V1
COMING SOON
Head on over to the official thread for unCoRrUpTeD Dual Boot >>>>>>>> Dual Boot
Reserved for no reason at all.
Maybe i can find a use for it
unCoRrUpTeD said:
Reserved for future use
Click to expand...
Click to collapse
HELL YEA!!! been waiting for this man..you are awsome! look forward to the release with anticipation. I did want to ask..whats a sufficient Micro Sd card to you(size wise)? i currently have a 2gb with about 1gb left would that be enough or should i go buy a 4gb?
+1 on this, will be really useful! Thanks for your work!
t12icky0 said:
HELL YEA!!! been waiting for this man..you are awsome! look forward to the release with anticipation. I did want to ask..whats a sufficient Micro Sd card to you(size wise)? i currently have a 2gb with about 1gb left would that be enough or should i go buy a 4gb?
Click to expand...
Click to collapse
I currently have the partitions for /system and /data set as 200Mb. i am going to try and add on more for /cache, but I am looking into making it as small as possible, since many would not be installing a lot of extra apps. It could be as small as 330Mb total.
so will i need that APPS2SD thing for this?
t12icky0 said:
so will i need that APPS2SD thing for this?
Click to expand...
Click to collapse
No. I will have instructions on setting up your sdcard
Right now my script is linux based. I'm not sure how much can be done with a batch script, but it will direct you in what you will need to do.
unCoRrUpTeD said:
No. I will have instructions on setting up your sdcard
Right now my script is linux based. I'm not sure how much can be done with a batch script, but it will direct you in what you will need to do.
Click to expand...
Click to collapse
sweet..your the man..cant wait!
One important thing I would like to propose here for the developer is a "standard" location somewhere on the SD card which would keep all the common data such as contacts, recent sms, call logs, etc. so that multi boot environment can share data without loss or duplicates.
In other words, boot to CM6 tonight and in two days when you decide to go back to stock ROM, all your sms, phone calls and such are picked up right where you left them in CM6 and vice versa.
Other than that, this sounds like an awesome thing. Can't wait to have the phone boot one ROM for Monday, another for Tuesday, and another for Wednesday and another...
obsanity said:
One important thing I would like to propose here for the developer is a "standard" location somewhere on the SD card which would keep all the common data such as contacts, recent sms, call logs, etc. so that multi boot environment can share data without loss or duplicates.
In other words, boot to CM6 tonight and in two days when you decide to go back to stock ROM, all your sms, phone calls and such are picked up right where you left them in CM6 and vice versa.
Other than that, this sounds like an awesome thing. Can't wait to have the phone boot one ROM for Monday, another for Tuesday, and another for Wednesday and another...
Click to expand...
Click to collapse
Not really possible. Different rom versions (2.1 vs 2.2) store the data in different formats. You'll have to rely on something like titanium backup to handle it.
How exactly is the dual-booting done? Does the batch script need to be controlled from the computer, or have you made a custom bootloader for on-the-fly switching?
HeroMeng said:
How exactly is the dual-booting done? Does the batch script need to be controlled from the computer, or have you made a custom bootloader for on-the-fly switching?
Click to expand...
Click to collapse
very good question
It's pretty simple if you have ever extracted the ramdisk and kernel from boot.img
The recovery has not been modified and the only time a computer is used is to setup the ROM the first time. You have to modify the boot.img from the ROM you want to installed on the sdcard. Once it has been changed, all you do is flash the boot.img of the ROM you want. I have mine setup where everything for the ROM is stored on the sdcard (/system, /data, and /cache) but have not been able to test out cache yet.
The reason for a non modified recovery is so that it can be done on any android phone.
I may put up a way to do this while I look into the script.
that is awesome you got so far so quick. i was hoping the squashfs tip would help you out. cant wait to see what approach you took.
unCoRrUpTeD said:
It's pretty simple if you have ever extracted the ramdisk and kernel from boot.img
The recovery has not beenmodified and the only time a computer is used is to setup the ROM the first time. You have to modify the boot.img from the ROM you want to installed on the sdcard. Once it has been changed, all you do is flash the boot.img of the ROM you want. I have mine setup where everything for the ROM is stored on the sdcard (/system, /data, and /cache) but have not been able to test out cache yet.
The reason for a non modified recovery is so that it can be done on any android phone.
I may put up a way to do this while I look into the script.
Click to expand...
Click to collapse
Oh, I see how you do the dual boot now. But I have one more question. How exactly do you get the rom on the SD? Do you use an ext partition or just put it on the FAT partition? Or is there some other partition type that I haven't heard of?
Sent from my Hero. It has a mind of its own
HeroMeng said:
Oh, I see how you do the dual boot now. But I have one more question. How exactly do you get the rom on the SD? Do you use an ext partition or just put it on the FAT partition? Or is there some other partition type that I haven't heard of?
Sent from my Hero. It has a mind of its own
Click to expand...
Click to collapse
Since everyone has a different size sdcard and most do not want to format the sdcard completely I will provide instructions on how to partition it correctly.
t12icky0 said:
HELL YEA!!! been waiting for this man..you are awsome! look forward to the release with anticipation. I did want to ask..whats a sufficient Micro Sd card to you(size wise)? i currently have a 2gb with about 1gb left would that be enough or should i go buy a 4gb?
Click to expand...
Click to collapse
Go on buy.com and get a 16gb sdcard for about 35 bucks, jesus lol !!!
CrashV2010 said:
Go on buy.com and get a 16gb sdcard for about 35 bucks, jesus lol !!!
Click to expand...
Click to collapse
lol..i dont use that much space...as you can see i have 1gb left on my
2gb..LMAO! i would have like prolly 15gb left on it. So it would be pointless for me to get a 16gb.
t12icky0 said:
lol..i dont use that much space...as you can see i have 1gb left on my
2gb..LMAO! i would have like prolly 15gb left on it. So it would be pointless for me to get a 16gb.
Click to expand...
Click to collapse
I have an 8GB class6. I have used about 4GB.
Post #2 has steps on setting up the sdcard
Just wondering but whats the plus side to this as opposed to just having different nandriod backups to flash between? I know it would be faster to boot but imo that's not woth all the partitioning of the sd card and what not. Now if it allowed you to run Windows Mobile roms from the SD then that would be awesome. I had a dual boot on my old HTC diamond and thats where I first discovered Android
Hi, I'm writing because nor the xda search nor google could pinpoint if a thread for this on our sgs4g existed.
I want to know if anyone has tried resizing the default partition sizes, or if it is even possible. I remember on my memory-starved HTC Hero this would be the only way to install apps comfortably without a2sd.
Maybe putting the /system partition on a diet and getting of nonessential apps would give us a few megabytes on the /data partition.
I'm a little oblivious to the situation, not being a dev, but just a curiosity.
Thanks in advance.
overthinkingme said:
Hi, I'm writing because nor the xda search nor google could pinpoint if a thread for this on our sgs4g existed.
I want to know if anyone has tried resizing the default partition sizes, or if it is even possible. I remember on my memory-starved HTC Hero this would be the only way to install apps comfortably without a2sd.
Maybe putting the /system partition on a diet and getting of nonessential apps would give us a few megabytes on the /data partition.
I'm a little oblivious to the situation, not being a dev, but just a curiosity.
Thanks in advance.
Click to expand...
Click to collapse
me and krylon already researched this actually by lowering the cache size and extending it to the data parttion we had the phone up to 1.3 gb of storage the issue lies in resizing the parttion requires you to modifiy it and flash customized bootloaders as the parttion info is stored in the sbl and boot files. It can be done however if you need to odin back without a changed pitt file you run into a host of issues
Ah, this would get a lot of people bricked if ever they would try to odin back to stock..
Might cause more problems than solve right now..
Good to know it isn't impossible, thanks
Sent from my SGH-T959V using XDA App
overthinkingme said:
Ah, this would get a lot of people bricked if ever they would try to odin back to stock..
Might cause more problems than solve right now..
Good to know it isn't impossible, thanks
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Its not impossable just not pratical
Sent from my GT-9101 using XDA Premium App
Noticed today I'm able to move almost all of my apps to SD and not just the supported ones without having done anything but installing a rooted stock ROM and some standard goodies (SU, BusyBox, ROM Manager and Titanium Backup). Wondering if it was enabled by any of the above? the rooted ROM? or the stock ROM?
any takers?
Titanium backup, in "batch", has option to move all apps to either sd or internal memory.
Sent from my myTouch_4G_Slide using xda premium
It's not true A2SD. Just a bunch of buggy symlinks in /data and incomprehensible files in /sdcard/.android-secure that Google is trying to pass off as A2SD.
Sent from a message in a bottle.
blackknightavalon said:
It's not true A2SD. Just a bunch of buggy symlinks in /data and incomprehensible files in /sdcard/.android-secure that Google is trying to pass off as A2SD.
Sent from a message in a bottle.
Click to expand...
Click to collapse
thanks. i rooted my phone right after the first stock boot so i couldn't tell if it came that way. It's just odd coming from 2.2 that everything all of a sudden is now movable, despite being not true a2sd.
psychedel!k said:
thanks. i rooted my phone right after the first stock boot so i couldn't tell if it came that way. It's just odd coming from 2.2 that everything all of a sudden is now movable, despite being not true a2sd.
Click to expand...
Click to collapse
I know. Just because a bunch of people find hitting "partition SD card" in ClockworkMod Recovery too difficult doesn't mean those of us who want the full potential of our phones unlocked should suffer, but we're stuck until someone finds us the mountpoint for sd-ext.
blackknightavalon said:
I know. Just because a bunch of people find hitting "partition SD card" in ClockworkMod Recovery too difficult doesn't mean those of us who want the full potential of our phones unlocked should suffer, but we're stuck until someone finds us the mountpoint for sd-ext.
Click to expand...
Click to collapse
you all need to check out link2sd (free app) it will let you install apps to ext partition. I myself use it and have a 8gb ext3 partition with over 550+ apps/games installed. It also lets you decide if you want to move dalvikcache and library files to ext to save more internal space. I used mini tool partition app on my pc to create a larger ext partition then cwm would allow.
Sent from my LG-P999 using xda premium
d12unk13astard said:
you all need to check out link2sd (free app) it will let you install apps to ext partition. I myself use it and have a 8gb ext3 partition with over 550+ apps/games installed. It also lets you decide if you want to move dalvikcache and library files to ext to save more internal space. I used mini tool partition app on my pc to create a larger ext partition then cwm would allow.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I'll try it on my days off. Thanks for the tip!
Sent from a message in a bottle.
blackknightavalon said:
..we're stuck until someone finds us the mountpoint for sd-ext.
Click to expand...
Click to collapse
sorry can you explain how and where we're stuck on and is that specific to our device?
blackknightavalon said:
I know. Just because a bunch of people find hitting "partition SD card" in ClockworkMod Recovery too difficult doesn't mean those of us who want the full potential of our phones unlocked should suffer, but we're stuck until someone finds us the mountpoint for sd-ext.
Click to expand...
Click to collapse
psychedel!k said:
sorry can you explain how and where we're stuck on and is that specific to our device?
Click to expand...
Click to collapse
WIP Memory Address Listing
You need to know where to put and access the data, explicitly, in order to be able to use that location.
Android does this by using mount-points, which translates to the memory address where it should be looking for the information.
The thread I linked to is one I started so that we can discover them all, and what mount points correspond to what memory address.
Please make sure to read post number 8 in the thread by dhkr234 which spells out a good caution about using memory addresses directly and why you should be using mount points instead.
If anyone makes any headway in learning anything we don't know so far, please post it in that thread so we can get a comprehensive listing of mount points and what memory addresses they correspond to.
I've been extremely busy on other projects, but if someone is going to come by and make A2SD available for us, having a road-map for them to follow already sitting here will make their life a lot easier. ( ...and maybe encourage someone to do it because the info is sitting there. )
...and yes, it is specific to our device. Every device addresses the internal memory differently and that makes the mount-points unique to each and every device.
gotcha, so...piecing this all together, does that mean that a true A2SD shouldn't rely on symlink at all and Link2SD (what d12unk13astard recommended) is essentially just another hack?
psychedel!k said:
gotcha, so...piecing this all together, does that mean that a true A2SD shouldn't rely on symlink at all and Link2SD (what d12unk13astard recommended) is essentially just another hack?
Click to expand...
Click to collapse
The real A2SD is not "just another hack," it's one of the ORIGINAL post-root hacks pioneers like JesusFreke came up with. It allows you to put your apps on an EXT partition of your SD card, and you can resize that partition if your computer runs a Linux distribution.
blackknightavalon said:
The real A2SD is not "just another hack," it's one of the ORIGINAL post-root hacks pioneers like JesusFreke came up with. It allows you to put your apps on an EXT partition of your SD card, and you can resize that partition if your computer runs a Linux distribution.
Click to expand...
Click to collapse
that i got, and sorry for being a pain..so then what difference does having a mountpoint or not make?
psychedel!k said:
that i got, and sorry for being a pain..so then what difference does having a mountpoint or not make?
Click to expand...
Click to collapse
Read the previous posts.
psychedel!k said:
that i got, and sorry for being a pain..so then what difference does having a mountpoint or not make?
Click to expand...
Click to collapse
Either:
blackknightavalon said:
Read the previous posts.
Click to expand...
Click to collapse
Or read this one again:
http://forum.xda-developers.com/showpost.php?p=19163237&postcount=8
dhkr234 said it good there.
I linked so someone who wants more of an explanation can follow and read up.
In short, you can very easily write to the wrong memory address.
This means:
Installing some silly game over parts of both your boot partition and recovery partition would give you a cool slide-paperweight.
Mount points prevent this from happening by ensuring the data is written to the proper memory addresses.
Has anyone tried to repartition our /system and /data folders to create an /emmc partition for our phones? Seems like OE partitioning scheme is a huge waste of space and we could better utilize the extra space if it was in user mountable partition.
This should be easy to do via recovery yes?
Sent from my MB865 using xda premium
unsivil_audio said:
Has anyone tried to repartition our /system and /data folders to create an /emmc partition for our phones? Seems like OE partitioning scheme is a huge waste of space and we could better utilize the extra space if it was in user mountable partition.
This should be easy to do via recovery yes?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Yes both lfaber06 and I sort of do something similar, with the way we have safestrap setup, but we use the SDcard instead. The one issue I see with this is what the future brings for this phone, like what moto might do for us with ICS, and such, what may be needed in these partitions to make it work. Other that that I don't see an issue, but you will have to change a ton of start scripts if the partition numbers change.
Jim
Sent from my MB865 using xda premium
I don't think you understand, I want the space to be user accessible, like I have on my nook. I flashed a custom repartition from cwm to resize data and media partitions. The /emmc partition is a fat32 partition I believe (on my nook anyways). I've never even come close to filling my 2gb data partition, and now I have 4gb of space for music or videos storage.
unsivil_audio said:
I don't think you understand, I want the space to be user accessible, like I have on my nook. I flashed a custom repartition from cwm to resize data and media partitions. The /emmc partition is a fat32 partition I believe (on my nook anyways). I've never even come close to filling my 2gb data partition, and now I have 4gb of space for music or videos storage.
Click to expand...
Click to collapse
No, I don't think you understand what that really does under the covers. Both lfaber06 and I have been working on this device for a while, we are the ONLY two devs currently working on this device. What I am telling you is that if you change the size of ANY of the internal partitions, It might effect the ability to update to another version of Android. Your Nook, is not a Mototrola device, and Moto has completly messed with/up android, and therefore it is not safe to do what you are saying. No matter what you can not get access to the internal partitions, yes on AOSP devices / devices that can be AOSP (the nook is one), you can do those things. The Atrix2 still has a locked bootloader, so we are stuck with their kernel, and version of android. To do what you are saying you will need to have an AOSP kernel, and have MANY init scripts updated to understand the new partition table. It is not as easy as you make it out to be.
Okay, I was under the impression with rw abilities on /system and /data partitions we also have the ability to mount, unmount; also giving us the ability to edit the partition blocks via bootstrap.
Ok how about this, there is a guy in the Nook Tablet forum (locked bootloader, like us) who had the idea of basically running a fat32 "img" that in the /data (ext4) partition to that would mount via a script and be user accessible? That would be possible I would think.
unsivil_audio said:
Okay, I was under the impression with rw abilities on /system and /data partitions we also have the ability to mount, unmount; also giving us the ability to edit the partition blocks via bootstrap.
Ok how about this, there is a guy in the Nook Tablet forum (locked bootloader, like us) who had the idea of basically running a fat32 "img" that in the /data (ext4) partition to that would mount via a script and be user accessible? That would be possible I would think.
Click to expand...
Click to collapse
Yes you do have access to all of those things with root, but Moto has done so much customization to this thing, that would not be safe.
Yes, that is also something that lfaber06 and I have thrown around as well, the logistics of it need to be worked out for our phone, and the proper init scripts need to be put together.
Are you up for the task? I only ask because he and I are currently working on porting cm7 and cm9 to our phone, which is a huge task. I can help you out, but I just can't take on anymore projects for this phone at the moment, since I have 5 different things I am working on for us right now.
I am definitely down to help, still going to be a bit of a learning curve for myself. Still pretty new to linux/android.
unsivil_audio said:
I am definitely down to help, still going to be a bit of a learning curve for myself. Still pretty new to linux/android.
Click to expand...
Click to collapse
PM me, with as much info as you have about this, preferably any links that you have read, and I will help you develop a game plan, and what you will need to make this hack happen. You will have to do some research on your own, and I can help with the Linux/Android part, and help you figure out what you will need to do. I am also not sure on the what kind of speed to expect from something like this, so that will also be something to look into, since this will be a virtual disk file.
SWAP on internal
Extend your RAM with very quick internal SWAP
v0.5 alpha
For the moment, the script is confirmed to work only on ROMs with the chinese x-part (or data2ext) by Atroy script only (read at the end of this post for alternative).
The only ROM I am aware of using this script out of the box is the excellent MIUI XJ x-part.
However, I intend to develop a non-loop based version shortly. It should will be compatible with most ROMs, so stay tuned.
What and Why
I decided to make a script that places the swap file on internal memory. Many people place it on SD card, but to me it seems somewhat pointless, as it hardly offers sufficient performance.
However, placing it on the internal memory makes it a much more interesting concept, because it has much better random read/write performance than even the fastest SD cards.
Warning: placing SWAP on internal memory will subject it to frequent read/write operations which in theory shortens lifespan of internal memory chip which you cannot replace. This is because flash memory has limited number of write/read cycles to it. So, consider yourself warned.
HOWEVER:
1 - although true, in reality I have been unable to find any case of this actually affecting anyone's phone. There is very limited amount of data documenting real-life effect of that process, but most likely your device will be long gone before the internal memory will show any signs of wear.
2 - the script recreates the swap file on each boot using different physical blocks of memory - this means not the same blocks are always used. More on this in 'Do it right' section.
Do It Right
1. 16-32 MB of swap should suffice. If you think you need more, you are probably wrong. NEVER use all available internal space. The larger the proportion difference between swap size and total free space on the internal data partition, the more breathing space your internal memory gets, as this allows the swap file to be moved around upon every reboot, which, in turn, will make it use the same blocks more rarely, and thus extending memory chip lifespan.
2. Get rid of bloat you don't use from the system partition, ie: ringtones, live wallpapers, useless system apps. Then create a custom
hboot with smaller system partition and larger data partition. You can do it using this (also attached to this post).
3. Play around with swappiness parameter. Still, the default set by the script should serve you well. But if you are paranoid, you can use it to further decrease how often system will write to swap.
Removal
Disable execution flag on the scipt in /system/etc/init.d and delete swap.img from internal data directory (on x-part scripts it is /mnt/asec/mtddata/ )
v0.5 alpha
* first public release
* loop device version only
Click to expand...
Click to collapse
x-part Impacted script (80% chance of rendering your ROM unbootable)
I attached a data2ext script which should offer better performance and battery life than some other a2sd scripts.
You are free to try and flash it on your ROM, but there is a good chance it won't boot any more - this is a very alpha version and I am not working on it at the moment.
Do not post complaints about it here. I only want to hear from you if it works!
So this allocates a part of your internal memory for random access? Nice.
I personally don't need more RAM, but this could be useful.
This sounds really good to my ears :good:
I will keep an eye on it.
Edit:
A small question:
So is it possible to use this for any rom if you are using data2ext for it?
Or atm only for miui xj?
Androidmarketuser said:
A small question:
So is it possible to use this for any rom if you are using data2ext for it?
Or atm only for miui xj?
Click to expand...
Click to collapse
You have to use Atroy's data2ext, which is virtually impossible to obtain because it was developed as part of chinese MIUI rom and never released as a separate script.
However, I have been working on it and I am attaching an alpha version of my adaptation of this script to the first post
Let me know if it works, but there is a good chance your ROM will not boot any more.
impactor said:
However, I have been working on it and I am attaching an alpha version of my adaptation of this script to the first post
Let me know if it works, but there is a good chance your ROM will not boot any more.
Click to expand...
Click to collapse
Thanks for your answer
I tried to install it on CM10 by vj but it didn't work. Here are my steps:
Wiped everything except sd
Installed rom, then data2ext script and finally the swap script.
I'm on a ext4 partition if it matters.
I think (not really sure) one script has created two folders: /data/ and /data-app/ on sdcard.
Or did I just install it the wrong way?
Edit: The problem was as you expected that it stucked at HTC bootlogo.
Androidmarketuser said:
Edit: The problem was as you expected that it stucked at HTC bootlogo.
Click to expand...
Click to collapse
If you want to try x-part script, then do not flash swap script until you confirm the x-part rom works.
Try with some GB rom. Maybe you'll have more luck.
impactor said:
If you want to try x-part script, then do not flash swap script until you confirm the x-part rom works.
Try with some GB rom. Maybe you'll have more luck.
Click to expand...
Click to collapse
I'll try it out that way on JB first (I am addicted to the new design, can't go back:crying, if it doesn't work I will try it out with 2.3 anyway.
---------- Post added at 08:45 PM ---------- Previous post was at 08:31 PM ----------
Ok on JB the data2ext script doesn't seem to work, I can't boot.
I will try it out later with a GB rom, propably EuroSkank
Hmm still doesn't work.
I tried MW7 on Redux2 but stucks at boot logo...
Custom hboot maker link from thalasmus blog is dead!
Can someone plz attach it here!
Sent from my HTC Desire using xda app-developers app
vasili_defy said:
Custom hboot maker link from thalasmus blog is dead!
Can someone plz attach it here!
Click to expand...
Click to collapse
Attached.
Don't have swap on internal! The number of read/writes will just kill your nand by creating loads of bad blocks.
Just my 2 cents
Kind Regards
Dave
topgeardave said:
Don't have swap on internal! The number of read/writes will just kill your nand by creating loads of bad blocks.
Just my 2 cents
Click to expand...
Click to collapse
And pray tell, apart from hearsay, what else do you have to support the claim that it will occur within foreseeable lifetime of the device?
I'd love to learn.
impactor said:
And pray tell, apart from hearsay, what else do you have to support the claim that it will occur within foreseeable lifetime of the device?
I'd love to learn.
Click to expand...
Click to collapse
After flashing ROMs on my Desire for nearly 2 years I'm starting to get bad blocks on my nand. Having a swap partition on internal would accelerate the process of getting more bad blocks. That's what I think anyway. Check your recovery.log for bad blocks next time you wipe your phone.
Kind Regards
Dave
Sent from my HTC Sensation using xda app-developers app
I tried this on Alex-V 1.8 and nothing happened
probably did something wrong
I'll try again later
topgeardave said:
After flashing ROMs on my Desire for nearly 2 years I'm starting to get bad blocks on my nand. Having a swap partition on internal would accelerate the process of getting more bad blocks. That's what I think anyway. Check your recovery.log for bad blocks next time you wipe your phone.
Kind Regards
Dave
Click to expand...
Click to collapse
Thanks for the heads-up. But I gave a clear warning about in the first post. After two years, my desire has 4 bad blocks, which amounts to less than 0.5mb of internal space (less than 0.1%). Everyone should make a concious decision about using internal swap.
It will degrade the memory chip, yes, but is the degradation significant enough to care? Everyone has to decide for himself.
impactor said:
Thanks for the heads-up. But I gave a clear warning about in the first post. After two years, my desire has 4 bad blocks, which amounts to less than 0.5mb of internal space (less than 0.1%). Everyone should make a concious decision about using internal swap.
It will degrade the memory chip, yes, but is the degradation significant enough to care? Everyone has to decide for himself.
Click to expand...
Click to collapse
how can I check if it's running on my rom...?
Balino said:
how can I check if it's running on my rom...?
Click to expand...
Click to collapse
Go into terminal and run "free"
impactor said:
Go into terminal and run "free"
Click to expand...
Click to collapse
It says swap 0... I think woh's roms doesn't support swap....