Related
I'm wondering if it's possible to create an ext3/4 partition on the SD-card and use it for files over 4gb. The main reason I want this is to play with Backtrack 5 for the ARM architecture. I'm guessing it should be as simple as partitioning my SD-card w/ a Fat32 partition as the first partition and then ext3/4 as my second and then adding a mount option into the fstab file. Just wanted to run it by anyone else that has already done it, or knows a better way.
PS. In case anyone else is interested, here's a thread with partial instructions on install Backtrack (if you're familiar with Linux, figuring out the rest shouldn't be difficult): http://forum.xda-developers.com/showthread.php?t=1074723&highlight=backtrack
Edit: Just found this: http://denniskuntz.com/blog/2011/05/11/backtrack-5-on-the-nook-color/ So, it seems it's possible. But, still have the question of can you have both a FAT32 and a ext2/3/4 partition on there and keep your nook functional as normal, but have a separate partition to run BT5 off of?
Hi there,
Is there a way to make the add the internal SD card to the main memmory? So that there would not be an internal SD card anymore?
I do not mean swapping the moutpoints around so my External_SD becomes my primary and my internal my second....
I want to get rid of the internal one alltogether (adding it to main memory).
I figure that I'll have to format the storage in a certain way... would that do it?
Can someone tell me step by step what to do?
I do have CW-mod installed.
I did search the forum, but couldnt find anything conclusive. Just hints that it should be possible...
If there already is a thread where all this is explained, please point me to it, because I couldn't find it.
Thanks,
Pfeffa-rah
I don't think this is possible , never heard of someone who did it
I have no idea how to do that. My question is... why would you want to do that?
Having an internal_sd partition adds the benefit of having big app data (such as those in Gameloft games) sit in a very fast partition and still be called "sddata".
Also, it's mountable via PC so everything in there can still be backed up. So it's best of both worlds really.
This was discussed some time ago in this thread: http://forum.xda-developers.com/showthread.php?t=1013575
There were ideas on how to remount the cards at boot. I myself come to the conclusion that since more phones start to behave in this way, app developers will have to start dealing with it. It just sucks they are mostly slow on the uptake. My main problem was the Spotify cache location being hard coded so I resorted to hack the Spotify apk.
PS. salisbury_steak: What is it with people like you that every time someone has a question on how to do something, your immediate response is "But why would you want to do that?!".
sorech said:
PS. salisbury_steak: What is it with people like you that every time someone has a question on how to do something, your immediate response is "But why would you want to do that?!".
Click to expand...
Click to collapse
That was actually an honest question.
I wanted to understand why he wanted to do it. (i.e. What would be the advantages of it.) There was no supposed sarcasm in there.
how about the ability to install 5x more applications?
Having that stupid 5gb partition as sd card and the real sd card as a sub folder is retarded...
My 32GB class 10 cars is a lot faster than the internal one.
The internal 5gb memory is MUCH TOO SMALL!!! Most apps don't allow you to store data on the external card. If you like me and many others install some games that download aditional data + a nav app that downloads maps for europe + some streaming music app like wimp that can cache music for offline play then you are ****ed with LG's setup.
The setup CM7 uses solves the main problem but effectively wastes the 5gb by mounting it at emmc where like 0,0001% of apps are able to access it.
So adding those otherwise wasted 5gb to the main memory would be great. But i have not seen any solution to that yet :-(
Thank you Gensplejs for explaining that to them. I had no idea how to reply to that since it seemed so obvious to me.
This thread was ment to be a question about how to do it and not to discuss the usefullness of it. That is where I lost the way in other threads...
So, thanks for your replys all (realy).
But now, back On-Topic:
How would I do it?
Sent from my LG-P990 using XDA Premium App
Please don't blame me if you tried it and you screwed up your phone.. It's your choice...
Well, I don't know if this would work, but this is how I would do it (accepting the fact that I'd loose almost 2GB of /data's free space):
1. Format your internal sd card to the same file system as your /data partition is (ext3 or ext4)
2. Copy every file from /data 1:1 to your sdcard (cp -R /data/* /sdcard)
3. I don't know when and where the partitions are mounted (maybe init.rc??)...anyways change the target there and let /data point to the internal sd card partition (so it is ensured that it is mounted automatically to the new location)
4. Reboot and keep your fingers crossed
I think i figured how to do it in theory. First we need some free space at our microsd to cp /data. Then we should repartition with fdisk /dev/block/mmcblk0p8 and p9 into one partition and change vold.fstab to mount only externalsd at /sdcard as we do when we swap partitions. In theory it should work but i cant test it right now or make a script since ve gone vacations and i dont have a pc to restore in case of error
I agree.. certain apps wont store to sdcard.. its better to use the whole 8gb as phone storage, and use external sdcard as default sdcard.
Sent from my LG-P990 using XDA App
What ive found till now is that sd swapping is easy. You can do it by tweaking only vold.fstab. But repatriationing is a pain in the ass. Looks like lg has "faulty" partitions or something and to do it you must mesh up with with almost half partitions.
I had to rebuilt boot lgdrm recovery data and sdcard to make em half work. So it probably isnt worth the trouble. Also I think init.rc is built on the boot. So just remounting internal sd to /data wont work either.
sectors is not space
it says 7996, so thats 8GB
i saw it in hurry. the brain sometimes belives whats he want to belive
sorry
New to XDA
Hello everybody,
I'm new to android and i'm trying to find out how to solve the problem posted in this thread.
I see you've got the awnser but i don't know how to do this.
I've been searching google and XDA for ever but i just can't find the awnser.
Could you make a step by step howto or point out to a post how to do this.
I mean converting your external sd to ext4 and change the mounting points.
I'm a complete nood, i didn't get adb to work on my pc, ext4 recovery is not for the p990 2x.
I've read something abbout changing fstap for swapping te mounting points for sdcard and emmc, witch is also ok for me, but formating to ext4... wel i frankly don't know how to do this.
I'm quite stuk on this.
The only partitioning experience i've got is Gparted in Ubuntu or repartitioning in Windows 7.
Thans in andvance!
Greetz,
JMG
http://android.modaco.com/topic/347...-partitions/page__gopid__1821791#entry1821791
check this
you can expand data partition , but there is a limitation of 1.75gb
Thanks davjan
Thanks davjan,
As far i can see it's indeed not worth it.
I wil have to go on and try to find out how to change the filesystem to ext4 and swap the internal and external sd.
That way i get more usable space instead of a big datastorage witch cannot contain program data.
But thanks for the quick reply.
Jean Michel Gaar said:
Thanks davjan,
As far i can see it's indeed not worth it.
I wil have to go on and try to find out how to change the filesystem to ext4 and swap the internal and external sd.
That way i get more usable space instead of a big datastorage witch cannot contain program data.
But thanks for the quick reply.
Click to expand...
Click to collapse
what rom are you using? is your phone rooted?
swapping internal with internal sd is very easy
and most of the roms here on xda are ext4 , if you instal one of them they autoconvert to ext4
Jean Michel Gaar said:
Thanks davjan,
As far i can see it's indeed not worth it.
I wil have to go on and try to find out how to change the filesystem to ext4 and swap the internal and external sd.
That way i get more usable space instead of a big datastorage witch cannot contain program data.
But thanks for the quick reply.
Click to expand...
Click to collapse
I you read the link provided you'll see that it makes what you want: grow internal filesystem = lower SDcard usable space. The only thing is that it doesn't seem possible is to use the whole space: system limitation. 75Markus tried high /system and /data values and phone didn't work.
See in his Mediafire Folder, 'Nvflash + guide for changing Partitions:
http://www.mediafire.com/75markus
Ext4 is now common with custom ROMs (in fact all of them).
You should search in sd-ext partition system, which was designed to artificially expand filesystem on older phones using an 'ext' partition. I didn't heard anybody using this on O2X.
If you use CyanogenMod based ROMs, your external card will be mounted ad /sdcard by default.
Switching internal and external SD
Thanks guy's,
I'll check it out.
I've been using cyanogenmod 7.1 stable with vorkkernel 20110208.
But that gave me batterydrains while using maps and nextvid ate the same time (while i'm driving).
Now i'm trying MIUI 1.11.11 with latest swift extreme.
But MIUI is very buggy so i'm thinking of going back to CM.
The only thing is that my phone won't boot with the latest vorkkernel.
Any one know how to increase internal storage? As iwanted to keep all the apps in internal storage instead of sdcard .
Advise against it. Set by default for system apps. Unless you flash custom rom. Best solution transfer apps to ext sd card
Sent from my GT-N7000 using XDA
jim2sad said:
Any one know how to increase internal storage? As iwanted to keep all the apps in internal storage instead of sdcard .
Click to expand...
Click to collapse
I don't think messing around with the partition is a good idea. But if you are a pro, that's what Android is for.
Sent from my GT-N7000
Well, yes and no. You have x GB of internal storage. That will never change. The deal is that you can only use a set amount of that x GB for apps and data. Without going into that much detail, though, a majority of that x GB is partitioned like this:
/system – x GB
/data – x GB
/cache – x MB/GB
/data is the only partition you can actually use for apps and data. So, to answer your question, you can make that /data partition larger. This requires root, though, as you suspected.
Resizing the partitions is much more advanced, though, and is not as simple as just installing an app. Whether you have a custom or stock ROM, make sure you leave yourself enough space where it needs to be.
So can I custom partitions my phone u may ask. At the moment it does not seem to be any tools or mod for doing this on N7000. But u can google "custom mtd partitions android" (or galaxy note).
But its not something I recommend but if u feel comfortable for doing this (if u find any ways to custom partitions) despite all the warnings that may appear on the guide, you can just go ahead and custom partition
Sent from my LT26i using xda premium
Thanks for all the feedback =]
i need to resize the partition for cm9. i only have 2.96 GB of space to use of my 32 GB touchpad? I need more than that, i am currently out of space on it. What do i do? important info may be i have tried to install Archlinux ARM twice, and each time it didnt work, but i believe a partition was made. I really do not want to lose progress on games that i have started on the device, or lose any files. How can i resize the partition on the touchpad, or make sure all of the partitions are gone?
cm9 help help
eddytheyeti2 said:
i need to resize the partition for cm9. i only have 2.96 GB of space to use of my 32 GB touchpad? I need more than that, i am currently out of space on it. What do i do? important info may be i have tried to install Archlinux ARM twice, and each time it didnt work, but i believe a partition was made. I really do not want to lose progress on games that i have started on the device, or lose any files. How can i resize the partition on the touchpad, or make sure all of the partitions are gone?
Click to expand...
Click to collapse
Have you tried the directions for adding partition size for the CM7 mod?
You will loose everything but if you use a back up program like titanium backup you can back up all you data from games and restore it when you are done!
I used the cm7 size partition on my touch pad and i have 8gigs for android now. The size is just a file you flash. The one i used was for a 2 gig increase and i flashed it 4 times.
wfooffroad said:
Have you tried the directions for adding partition size for the CM7 mod?
You will loose everything but if you use a back up program like titanium backup you can back up all you data from games and restore it when you are done!
I used the cm7 size partition on my touch pad and i have 8gigs for android now. The size is just a file you flash. The one i used was for a 2 gig increase and i flashed it 4 times.
Click to expand...
Click to collapse
Never heard of this. Could you elaborate?
I've been thinking about this for a few days now. Then, today, xda posted an article on repartitioning the Xperia to gain some advantage. So it seems like a good time to pose this question for us HD+ owners.
This a "feasibility study" question. I'm not a developer. I can hardly hack my way though Mint, let alone the HD+. I'm asking if the following possible?
(If yes, maybe a nice developer will do it for us? )
Can we shrink and repartition the /factory partition in the HD+ (as they shrink partitions in the Xperia) and use the leftover space as /swap?
Background
I've been reading leapinlar's excellent treatises on the partition structure in the HD+ (see Item 16) and how the /factory partition, meant for automatic disaster recovery, doesn't do us much good if you've installed a custom ROM and a custom recovery. (See all of Item A12.)
Among other things, the /factory partition contains an image of the stock B&N ROM. Which will cause bootloops if triggered when you're running CM.
But, if I understand it correctly, the /factory partition isn't a total waste. It duplicates some important data from the /rom partition (devconf), which could come in handy IF you put the stock recovery back on in an attempt to fix your HD+. (Then it could rebuild the /rom partition if it had become corrupted.)
So, as it stands now, /factory is 448 MB that's mostly useless to us. Can't we put it to good use? Like /swap? Or direct zRAM to it?
Leapinlar has already created some repartitioning tools, as has the Xperia dev now. So I'm hoping a lot of the hard work has been done already.
Proposal
(I apologize in advance is my terminology isn't exactly correct.)
Is it possible to:
1) remove the factory.zip from the /factory partition and then shrink the partition to accommodate only the /rom backup files. (I'm thinking that all factory zips are the same size, so once the new smaller partition is calculated, it ought to be the same for everyone's HD+);
2) create a new partition from the left over space, calling it (new) partition #11;
3) format partition #11 as swap
4) easily tell CM 10 or CM 11 to use the /swap? I'm hoping this can be done with just a init.d script. (Maybe an fstab tweak too?)
5) Or perhaps dedicate #11 for zRAM, as a kernel developer has done with useless space in the Galaxy Tab 2. In essence, we'd have almost 1.5GB of RAM.
Feasible? Yes/No? I realize that dinking with partitions can damage my HD+. It's a risk I'm willing to take.
I'm not going to get involved with this, I'm just going to add a warning. The partition structure for the HD/HD+ is different than the Nook Color and most other devices. The NC and other devices like SDs use DOS partitioning. The HD/HD+ is like the Nook Tablet that uses GPT partitioning. The two partitioning schemes are not compatible. So don't try to use my tools in the NC forum. If you want to know more about GPT partitioning on the Nook Tablet and get some tools, search the Nook Tablet forum.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The partition structure for the HD/HD+ is different than the Nook Color and most other devices. The NC and other devices like SDs use DOS partitioning. The HD/HD+ is like the Nook Tablet that uses GPT partitioning. The two partitioning schemes are not compatible.
Click to expand...
Click to collapse
Good to know! Now we have more data than we had before.
Looks like a lot of the work has been done already
So, I found this thread in the xda forums all about nook tablet partitions. They even talk about resizing! (Or at least, about making a different size /userdata partition.)
There is also this here about repartitioning Nook partitions.
Looks like parted would be easier for what I'm looking to do, shrink the /factory partition and create a new partition.
I read here that I can use a live Linux CD to mount the factory.img. From there, I presume I can delete the factory.zip and create a new image?
I'm not a linux geek, but I presume I need to be on a live Mint CD to use parted in ADB? (Update: Apparently I am to use the Android SDK for ADB in Windows. Downloaded already. Am climbing the steep learning curve.)
First half of Step 1, Done
Well, it took longer than it should have, but I made a new, smaller factory7.partition.img file. It's 1 MB.
I started by booting a Mint 16 Live CD.
Then I mounted the OEM factory partition image I made beforehand using the dd command, per leapinlar's instructions. (See his Item 16.)
Code:
sudo mount -o loop partition7.factory.img {some.folder}
That image contained 4 zips: factory,zip; fsck.zip; rombackup.zip; romrestore.zip.
Dummy me, I tried deleting the factory.zip inside the mounted image. It occurred to me later that that would be like trying to delete a file from a mounted CDROM's iso image. Can't be done.
So I copied the 4 zips to a new folder. Then I could deleted factory zip, which was 433.3 MB.
That left less than 1MB for the other 3 zips.
If there's an elegant way of modifying an .img and resaving it, I couldn't find it. (I spent a lot of time with mkfs.yaffs2. But this .img was not a yaffs.(Didn't pass a "sanity check" when I tried to mount the new .img I had made with mkfs.yaffs2.)
So I brute forced an imaging solution by copying the 3 copied zips to a 1MB ext4 partiton on a USB stick. (I made the partition with gparted and used chmod 777 to clear permissions in the partition.)
Then I made an image of the new 1MB partition using the dd command. In my case
Code:
sudo dd if=/dev/sdd2 of=new.partition7.factory.img
(I probably don't have the leading /'s right here. Am truly hacking my way through all this. I'm sure most of you could do this whole project in a few minutes.)
So now I have a shiny new 1MB custom factory image just wating to be used.
Update: I think I'll redo this, and leave 4 zips, in case the recovery mechanism is looking for a "factory.zip" I'll made a dummy file and archive it, calling it "factory.zip."
The next task is to get ADB working, delete the original large partition7 in the HD+, create a new 1MB partition7 in its place, and then restore my new image to partition 7 using the dd command in reverse.
After that, then to create partition11 out of the unallocated 432MB and format that as swap.
Update: It occurs to me that I will have to backup partitions 8, 9, and 10 with dd. Then I'll have to destroy them, recreate them in new locations, and then restore them. Fortunately, an xda developer has already written the instructions on how to do all this.
I see that CM 10 supports swapon, so I'm hoping it will be downhill after the partition work. I'm hoping CM will automagically find the new swap partition, once I enable swap.
If you know different, I'd appreciate hearing from you. Will using swap in this memory burn the memory out quickly?
Better yet, swap file instead of swap partition
So, I was thinking more about this idea and how I'd have to destroy and recreate p8, p9 and p10 to make a new swap partition at p11. Aside from that being a lot of work and more prone to errors with all those operations, a new p11 would never get TRIM'd by the OS.
So now the plan is to reduce /factory (p7) to 1MB and increase /system (p8) by 443 MB. Then I'll put a swap file in /system.
Only have to work on two partitions that way and /system gets TRIM'd. (Or at least Lagfix will trim it.)
Whatdaya think?
I suppose it's easy enough to put a swap file in /data to get a feel if there's any performance gain from swap in eMMC. Someone wanna show me the code to do this? (I've read about how to create a swap file. Not sure how to mount it at emmcblk10.) Never mind, Found it on xda! Am currently running 500MB swap on /data to see what it's like.
PMikeP said:
So, I was thinking more about this idea and how I'd have to destroy and recreate p8, p9 and p10 to make a new swap partition at p11. Aside from that being a lot of work and more prone to errors with all those operations, a new p11 would never get TRIM'd by the OS.
So now the plan is to reduce /factory (p7) to 1MB and increase /system (p8) by 443 MB. Then I'll put a swap file in /system.
Only have to work on two partitions that way and /system gets TRIM'd. (Or at least Lagfix will trim it.)
Whatdaya think?
I suppose it's easy enough to put a swap file in /data to get a feel if there's any performance gain from swap in eMMC. Someone wanna show me the code to do this? (I've read about how to create a swap file. Not sure how to mount it at emmcblk10.) Never mind, Found it on xda! Am currently running 500MB swap on /data to see what it's like.
Click to expand...
Click to collapse
I guess this is a dumb question, but if you can put a swap file in /system and /data, why can't you delete the factory.zip from /factory and put the swap there? Why create a new partition?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
I guess this is a dumb question, but if you can put a swap file in /system and /data, why can't you delete the factory.zip from /factory and put the swap there? Why create a new partition?
Click to expand...
Click to collapse
First, I'm abandoning my bright idea. Turns out that swap is slow (even on eMMC) and possibly destructive to the eMMC with all the writes. (Hmmm . . . I wonder how many writes /cache gets compared to a swap file? (IOW, would a swap file be any more destructive than cache is?))
There were 1 second pauses every now and then, presumably while swapping when I had a swap file mounted in /data. Even tho I could get more free memory with a swap file than with zRAM, zRAM is much faster. And since zRAM is supported by the OS, it's the path of least resistance for me.
But to answer your question, it's not a dumb question. I'm a dumb user.
First, I don't know how to mount the /swap on the /factory partition. Can it be done? I don't see /factory in root explorer when running. Whereas I can see /system and /data. (So, to use Windows talk, it seems like /factory is "hidden" when running the OS?) By the same token, I don't know if I can delete the factory.zip from /factory in situ. If it can be done, it probably requires ADB and fastboot (?). But I haven't learned about those yet. So I'd have to use my new image trick, from my post above, to "delete" factory.zip from /factory.
Second, even if I could mount a swap in /factory, I don't think I'd want to. (Although I agree it's be a lot easier (and less dangerous) than deleting and recreating partitions.) I don't think /factory gets TRIM' by the OS. And I presume I would want it TRIM'd every now and then or else the swap would get slower over time than it already is.
I notice that Lagfix offers to trim /system and /data (and /cache). But not /factory. As above, if /factory is not visible during operation of the OS, that would be one reason why Lagfix doesn't trim it.
Or it could simply be that Lagfix doesn't see the need to trim /factory. Since /factory is supposed to be static, there wouldn't be any reason for Lagfix (or CM) to trim it.
Whether /factory can be trimmed with the fstrim command while running, I don't know.
Anyway, my idea for swap wasn't such a good idea. So I've abandoned the idea.
It still bugs me, as an engineer who compulsively tries to optimize everything, to carry that wasted 443 MB around in /factory.
I don't think we need an extra 443 MB in /system or /data. (Or /cache.) But if we ever do, we know where to find it.
/factory is not automatically mounted in stock or CM. So to get access to it you would need to mount it with a script command. And I would assume you need script commands to set up /swap so that should not be a problem. But /factory is formatted fat32 and /data and /system are ext4 so that might interfere too.
And manual trim commands can be run to trim the mounted /factory. You don't need the app lagfix to do it.
But I agree, I'm not really sure you gain anything with swap on this device.
Edit: as PMikeP pointed out to me in a PM, I was mistaken. /factory is ext4, not fat 32. Thanks for the correction. That should make it easier.
Sent from my BN NookHD+ using XDA Premium HD app