Database Users

[Q] How much space is actually usable on Nexus 10?

Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?

isaacwg said:
Google advertizes that I can get up to 32GB of internal memory on the Nexus 10.
I am thinking about getting this tablet, but it doesn't have a MicroSD card slot, so I need to know this:
How much of the internal 32GB can I actually use?
Does the ROM take up some of that space, and how much?
Click to expand...
Click to collapse
29.71 GB of free space + you can get more via usb otg.

Not bad...
lKBZl said:
29.71 GB of free space + you can get more via usb otg.
Click to expand...
Click to collapse
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.

isaacwg said:
Well, that's not too bad. And USB OTG looks quite interesting.
Thanks for the quick reply.
Click to expand...
Click to collapse
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?

This may help you...
ClutchKargo said:
I ordered a USB OTG from Amazon but it's coming from China is there a USA source?
Click to expand...
Click to collapse
On Amazon's website, when looking at a product, under the "add to cart" box, there is another box labeled "More Buying Choices".
That is probably what you want.

So what about the ROM?
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?

16gig
What about 16gig version ?

Ashirmittal said:
What about 16gig version ?
Click to expand...
Click to collapse
13.05gb on my 16gig, but I have an USB otg so no worries for me as I have plenty micro SD cards for storage.
Sent from my Nexus 10 using XDA Premium HD app

isaacwg said:
OK, here is one thing that is not quite clear to me.
lKBZl, you said that the Nexus 10 has 29.71 GB of free space, but where is the ROM stored?
Am I right in assuming the ROM is stored on a separate partition, and the usable partition is 32GB?
So wouldn't that make the internal memory's real capacity larger than 32GB?
Click to expand...
Click to collapse
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.

trickster2369 said:
32 gb is the total size of the storage capacity.
29.71gb is what is left for you to use as you wish.
Of the 3 or so gb missing, part of that is the os partition (/system) that contains the rom, kernel, etc.
And a smaller portion of that is strictly from the format process, small files that allow the memory to work.
Click to expand...
Click to collapse
OK, thanks. That clears things up for me.

isaacwg said:
OK, thanks. That clears things up for me.
Click to expand...
Click to collapse
Lol I though you'd have understood that with the space left from the 29,71 to 32, it means that there is rom and etc.
If you guys want to buy an otg adapter, I recommend not to buy a cable like this: http://www.amazon.com/T-Flash-Adapt..._2?ie=UTF8&qid=1357413912&sr=8-2&keywords=otg
since then you won't be able to use a pendrive and a headphones. Something like this is better (in my opinion):
http://www.amazon.com/SANOXY-Micro-...F8&qid=1357413953&sr=8-7&keywords=otg+adapter

I looked at afew of the otg cables when I ordered my case, but none of them get any really good reviews. Maybe I am to picky dunno I will look to see if I can find any around where I live.

Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks

Gizmotech said:
Can someone with a Nexus 10 tell me how much total space is on the /system partition, how much on the /data partition and how much on the mnt/sdcard partition. Also of which how much of that is available on a clean phone on each partition. Thanks
Click to expand...
Click to collapse
Total values are what you're looking for.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks. And this is for a clean rom with nothing installed yet right?
It looks like /data and /sdcard are not separate partitions instead directories on the same partition unless you have binded the 2 directories Can someone confirm this please?

I'm a little late to the party but a 32GB once formated usually lose ~7% once formated as FAT/NTFS.
EXT4 should probavbly be no difference.
MB
->
300GB=279GB
320GB=297GB
400GB=372GB
500GB=465GB
1TB=0.931TB
2TB=1.86TB
3TB=279TB
->
PB
So the 32GB without any files* should have 29.7GB
*No OS or boot files etc.
It's not exactly 7% but it's close and easier to calculate than the "1024^1000=banana/shoe+cat=value".

Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.

Gizmotech said:
Thank you but I was more concerned with the partition sizes as if /system partition is full, it doesn't matter how much space you have available in /data or /sdcard, it won't allow to install apps or games. I can't understand why they didn't have one partition with directories instead of partitions. That way we wouldn't have issues such as free space on one directory/partition and full up on another. I think in this sense, the iphone storage management is better.
Click to expand...
Click to collapse
Apps (end user installed) aren't stored in the /system partition the OS is. Apps go in /data.. It would be insanely hard, and nearly impossible to fill up the /system partition.
The only phone I know (probably more) that has ever ran out of useful /system space is the Nexus One which is the reason Google stopped upgrading it because ICS wouldn't fit on the /system partition. End users got crafty though and figured out a way around the limitation by crafty partitioning magic with the Micro SDCard slot.

Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is because if you look at the storage info of my phone (screenshot below) /data partitiom and /sdcard partition are showing different storage capacity and usage whereas your nexus 10 shows those two to have identical capacity and usage.
My concern is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, which I think the configuration is on the nexus 10, it would still show available space as both directories combined would make one partition. Which would then leave me to wonder why didn't they do the same for my Galaxy Ace 2
Ignore sdcard 2nd part, this is created on removable sdcard for purposes of Link2SD app.

Gizmotech said:
Yes, but the Nexus 10 does not have an SD Card slot so there won't be any other way of expanding storage once the internal storage fills up. But I see what you mean about the /system partition.
Could never get my head around this Android partitions. So am I correct to say the APK and App data are stored in the /data partition? And Game that require additional download able content is stored in the /Sdcard partition?
Now my question is, is the /data partition and /sdcard partition two separate partitions or two directories on a single partition on the nexus 10? The reason why I am asking is if one partition is full up, and you may have useless space on the other partition where as if they were directories, either they will share the space on demand. Not sure if I am explaining it correctly but for example I have a Galaxy Ace 2 which if I was to fill up the /sdcard partition, and have a adequately free /data partition, then often that free space is useless for some apps as it requires available space on the /sdcard partition. Now if they weren't partitions and instead directories, it would still show available space as both directories combined would make one partition.
Click to expand...
Click to collapse
They are essentially in the simplest terms exactly as you described. Two folders pointing to the same partition. That is why you can wipe your "sdcard" but all your apps remain intact in /data even though it's the same partition.
The reason your Galaxy Ace is like that is because you have a legit removable SDCard storage and it isn't part of the internal storage.. This complication in partitions w/ real sdcards is why Google refuses to put SDCard slots on any of their devices.

Increase internal memory

Hello,
Is it possible to further.increase internal memory.
I have made link2sd, but want to increase more. Attach is my current memory status.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I want.to take 100mb from system and 50mb rom cache.
Plz guide me, thanks.
Sent from my HTC Wildfire using Tapatalk 2

bilal1947 said:
Hello,
Is it possible to further.increase internal memory.
I have made link2sd, but want to increase more. Attach is my current memory status.
I want.to take 100mb from system and 50mb rom cache.
Plz guide me, thanks.
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
It's impossible exept if you delete system media like ringtone.
Sent from my HTC Wildfire using xda app-developers app

after intstalling all my installed user apps, ie., 46 in numbers, i am left with 180mb free internal memory
I tried mtd partitioning and got more space but not sure as what exactly happened, as something weird has happened.
A) changed system partition size from 250 to 150, means 100mb here release.
B) changed cache partition size from 175 to 75mb, means 100mb here release.
C) i should get this 200mb as free in data partition apart from what free internal memory which is 90mb that i already have & all i got is 180 that means, an increse of 90mb only so where the rest of the space gone?
Anyhow, i am happy, how much total internal memory does Wildfire show and how much do you guys left with after installing all the apps?
Sent from my HTC Wildfire using Tapatalk 2

bilal1947 said:
after intstalling all my installed user apps, ie., 46 in numbers, i am left with 180mb free internal memory
I tried mtd partitioning and got more space but not sure as what exactly happened, as something weird has happened.
A) changed system partition size from 250 to 150, means 100mb here release.
B) changed cache partition size from 175 to 75mb, means 100mb here release.
C) i should get this 200mb as free in data partition apart from what free internal memory which is 90mb that i already have & all i got is 180 that means, an increse of 90mb only so where the rest of the space gone?
Anyhow, i am happy, how much total internal memory does Wildfire show and how much do you guys left with after installing all the apps?
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Default cache size is around 50mb,75mb is wayy to much.
I always have 10mb for cache.
Fir cm7,i recommend 140 10 mtd values.

What's going on? As u suggest i made system partition to 140 and cache partition 25, and see.what it does, 300mb cache.
And how come its using 75mb?
What i do now to get this cache to internal memory?, though free internal memory after all my apps is 220mb. That's enough.
Sent from my HTC Wildfire using Tapatalk 2

Most probably link2sd is showing it wrong. As i can see it is showing right values, i.e 300 mb internal memory.
So download some app called freespace from play store and check with it.
And you can never have 140 system+300 data+300 cache in 512mb ROM.

You are right.
Sent from my HTC Wildfire using Tapatalk 2

internal memory issues
Please help me!!
I have erased all phone data, set it back to factory data, wiped dalvik cache, data and EVERYTHING possible!! My phone is like new.
But it still says the avaiable space is 98.30MB!!!
Why is that and what can do??

t2oll said:
Please help me!!
I have erased all phone data, set it back to factory data, wiped dalvik cache, data and EVERYTHING possible!! My phone is like new.
But it still says the avaiable space is 98.30MB!!!
Why is that and what can do??
Click to expand...
Click to collapse
Two ways to increase:
No.1 Link2sd - via making partition of you sd card
Watch this video and you can do it, its easiest way.
http://www.youtube.com/watch?v=xxFizGRdYeM
No.2 re-partitioning of the original system & cache partition to its required size and automatically you will get the freed space for internal memory
http://forum.xda-developers.com/showthread.php?t=1233340
Must read this thread if lost, its a complete index related to wildfire
http://forum.xda-developers.com/showthread.php?t=1029318

Thank you very much!
I installed Storage Analyser and it shows I have 66MB of dalvik cache (data/dalvik-cache) and 29MB em data/data but then when I go to these folders using ES File Explorer, thee folders is 'empty'.
I will read the links you sent me and I hope it helps.

restarting issues
Deleted

Why system take 8GB space ?

I have note 2 LTE 32 GB model and i have flashed CM 10.2 but it say 24 GB is available for user? Why system take such huge space of 8Gb as i dont think CM 10.2 ROM use all of it. Where the rest of the space go ? My question is : Are these system partitions fixed in size no matter what ROM you flash? It will be alaways 8GB reserve for ROM whether stock or AOSP ?
Here is screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7105 using Tapatalk 2

go to adb shell,type "df "command,and you will see the usage of each diretory.

proxlwt said:
go to adb shell,type "df "command,and you will see the usage of each diretory.
Click to expand...
Click to collapse
Thanks and I did that and this one is what i get..i see that sysyem is using 2.3 gb but what are these first four in /mnt taking 893 mb each
Sent from my GT-N7105 using Tapatalk 2

Rajaasim1980 said:
Thanks and I did that and this one is what i get..i see that sysyem is using 2.3 gb but what are these first four in /mnt taking 893 mb each
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
The first thing to note is that 32GB internal memory is in reality 29.4GB (32000000000 bytes translates into 29.4 real GB).
So to add up:
- 24.2GB of user data
- 2.3GB for /system
- 1.2GB for /cache
- 0.5GB for /tombstone /firmware and /efs
--------------
- 28.2GB
/mnt/obb asec secure and fuse are all virtual mount points to various directories and their size is arbitrary
/dev is again virtual mount point for all hardware devices in your phone used to access various properties of devices - size arbitrary
All of them are temporary file systems created on every system start.
I don't know where is the 1GB of space that should be there and it's not only your problem. This is present on all systems that I have seen.
Look at this for example:
View attachment 2597562

mat9v said:
The first thing to note is that 32GB internal memory is in reality 29.4GB (32000000000 bytes translates into 29.4 real GB).
So to add up:
- 24.2GB of user data
- 2.3GB for /system
- 1.2GB for /cache
- 0.5GB for /tombstone /firmware and /efs
--------------
- 28.2GB
/mnt/obb asec secure and fuse are all virtual mount points to various directories and their size is arbitrary
/dev is again virtual mount point for all hardware devices in your phone used to access various properties of devices - size arbitrary
All of them are temporary file systems created on every system start.
I don't know where is the 1GB of space that should be there and it's not only your problem. This is present on all systems that I have seen.
Look at this for example:
View attachment 2597562
Click to expand...
Click to collapse
Thanks for explaining it .I cannot see your attached screenshot because its too tiny. Its stupid for manufacture to advertise memory as 32 GB when its 28 GB in reality.
What i actually dont get is no matter you use custom CM or stock sammy rom (with bloatware) you will get same free space eventhough CM ROMs are less in size.
Do you see any unnecessary partition there which need to be deleted ? ..these partition within partition i.e ,0,Sd card 1, emulated, legacy etc are very confusing
Sent from my XT1032 using Tapatalk 2

Rajaasim1980 said:
Thanks for explaining it .I cannot see your attached screenshot because its too tiny. Its stupid for manufacture to advertise memory as 32 GB when its 28 GB in reality.
What i actually dont get is no matter you use custom CM or stock sammy rom (with bloatware) you will get same free space eventhough CM ROMs are less in size.
Do you see any unnecessary partition there which need to be deleted ? ..these partition within partition i.e ,0,Sd card 1, emulated, legacy etc are very confusing
Sent from my XT1032 using Tapatalk 2
Click to expand...
Click to collapse
Er... you did click on it? It opens in overlay to display full screen...
The advertisement...
It's like with hard disks in modern PC, manufacturers advertise the disk as having 1TB of space, but they are counting it as 1.000.000.000.000 of bytes while in reality we are using binary computers that do not count that way - they count 2^10 = 1024 so you have to divide this 1.000.000.000.000 bytes by 1024 to get kilobytes = 976562500 and again by 1024 to get megabytes = 953674 and again by 1024 to get gigabytes to arrive at 931GB of real disk size. From that you have to subtract partition overhead (the system needs place to store info about your files) but that is dependent on the number of files you plan to put on the partition.
If you are really advanced user and not planning to ever flash back to sammy rom, you could repartition your internal memory to say decrease /system size to say 750MB and earn almost 1.2GB of free space. But it's dangerous and will void your warranty 100%
There are no unnecessary partitions, /system /data and /cache are necessary to functioning of any rom, all others are virtual partitions created using mount points and FUSE file system - the are also needed to work and they don't take any space. I can't find the missing 1GB of space.
The command "mount" that you execute not only shows typical partitions but also some "shortcuts" used by system to access different places in the internal memory and is not normally visible to end user - they are there to make life easier for programmers and advanced users. Us common folks just gets confused - it's like dissecting how your car engine works - not for everyone

mat9v said:
Er... you did click on it? It opens in overlay to display full screen...
The advertisement...
It's like with hard disks in modern PC, manufacturers advertise the disk as having 1TB of space, but they are counting it as 1.000.000.000.000 of bytes while in reality we are using binary computers that do not count that way - they count 2^10 = 1024 so you have to divide this 1.000.000.000.000 bytes by 1024 to get kilobytes = 976562500 and again by 1024 to get megabytes = 953674 and again by 1024 to get gigabytes to arrive at 931GB of real disk size. From that you have to subtract partition overhead (the system needs place to store info about your files) but that is dependent on the number of files you plan to put on the partition.
If you are really advanced user and not planning to ever flash back to sammy rom, you could repartition your internal memory to say decrease /system size to say 750MB and earn almost 1.2GB of free space. But it's dangerous and will void your warranty 100%
There are no unnecessary partitions, /system /data and /cache are necessary to functioning of any rom, all others are virtual partitions created using mount points and FUSE file system - the are also needed to work and they don't take any space. I can't find the missing 1GB of space.
The command "mount" that you execute not only shows typical partitions but also some "shortcuts" used by system to access different places in the internal memory and is not normally visible to end user - they are there to make life easier for programmers and advanced users. Us common folks just gets confused - it's like dissecting how your car engine works - not for everyone
Click to expand...
Click to collapse
Thanks for detail reply which make sense. These partitions were actually much simple in previous version of androids.
So no matter what ROM i would flash there will be same amount of free space available because there is fixed size partition in internal memory reserved for ROM/system irrespective of size of ROM. Right?
Sent from my GT-N7105 using Tapatalk 2

Rajaasim1980 said:
Thanks for detail reply which make sense. These partitions were actually much simple in previous version of androids.
So no matter what ROM i would flash there will be same amount of free space available because there is fixed size partition in internal memory reserved for ROM/system irrespective of size of ROM. Right?
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Right. The only advantage of CM is speed, in this case "Size does not matter"

CWM Flashable: Mount external USB storage to /data and /sdcard

The goal of this was to swap /data and /sdcard with usb storage so that i could install unlimited apps and games. Swapping them does come at the price of speed as the usb interface is not as fast as the internal storage. Bascially you could do the same thing with stickmount and link2SD, but then you have to deal with stickmount and link2SD....
This is based on croniccorey's "INT2EXT+" script located here: http://forum.xda-developers.com/showthread.php?t=1716124
Thanks to rbox for recovery and jocala for UUID idea.
Warning: This will make your fireTV run slower. This works best on a clean install, but should work either way. You may see a pixelated screen on first boot and it will take a few minutes while files are copied to USB, just be patient.
There are now 3 versions of the scirpt pick your poison:
1. the original MountDataToUSB which mounts your USB drive to /data (except /data/misc). This is the total solution for external usb drive hard drives plugged into powered hub only. External Hard Drives only, DO NOT USE WITH USB THUMB DRIVE.
2.. MountPartialDataToUSB Same as #1 except it leaves /data/misc /data/system and /data/data mounted to internal storage. The downside is when you install new apps some stuff does get installed to /data/data which takes up internal storage space. Tested with USB 2.0 thumb drive and UI seems as fast as stock.
3. MountMediaToUSB which mounts your USB drive to ONLY /data/media (and the fuse mount point /sdcard) expanding where game OBB files are stored (similiar to sticking an SD Card in your phone). This should be about as fast as stock fireTV except when accessing data off /data/media but this doesn't expand /data/app
I've made this into a CWM flashable now to simplify things. You need to have the following pre-requisites:
1. Rooted with rbox's CWM recovery installed
2. ext4 formatted usb drive I recommend using the full drive, but it should work as long as it's the first partition
(google how to do this).
3. This script won't work with multiple drives plugged in as it mounts /dev/block/sda1 which is the first drive detected Mounts by UUID now so you can use jocala's BusyMount script to mount other drives after.
4. The ext4 forrmatted drive must be the only drive plugged in when flashing the zip because it grabs the UUID off of it while flashing.
Click to expand...
Click to collapse
Instructions:
1. Plug in ext4 formatted USB Drive
2. adb reboot recovery
3. Factory Reset (optional but recommended, some users have reported errors if they don't. Also first boot will take longer while it copies all files from data). If you factory reset make sure you are blocking updates.
4. Flash zip in CWM. MAKE SURE THAT ONLY YOUR DRIVE YOU WANT AS DATA IS PLUGGED IN WHEN YOU FLASH v3.0 and newer zips THAT IS WHEN THE UUID IS READ and stored.
4. Reboot (first boot may take a few mins while files are copied, pixelated screen may display for couple minutes be patient). May be very laggy while it is downloading everything from the cloud to your usb drive, but should speed up a bit after it's done.
5. a. If using full data mount - Check System about for available disk space .
b. if using Media Mount only - run this command from shell and view available storage on media:
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 974M 48K 974M 4096
/mnt/secure 974M 0K 974M 4096
/mnt/asec 974M 0K 974M 4096
/mnt/obb 974M 0K 974M 4096
/storage/usb 974M 4K 974M 4096
/system 756M 723M 33M 4096
/data 5G 946M 4G 4096
/persist 7M 4M 3M 4096
/cache 756M 13M 742M 4096
/firmware 63M 7M 56M 16384
/data_fire 5G 946M 4G 4096
/data/media 15G 750M 14G 4096
/mnt/shell/emulated 15G 750M 14G 4096
/storage/emulated/legacy 15G 750M 14G 4096
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Details: When the script first starts it waits up to 30 seconds for /dev/block/sda1 to come up. If it doesn't come up (or if the usb drive is not plugged in) then it boots from internal storage. It then checks for the folder "/data" on the usb drive, if it doesn't exists it copies the files from the internal storage to the USB drive. Everything under /data is mounted to usb storage with the following exceptions /data/dalvik-cache /data/misc and /data/resource-cache
IMPORTANT: The internal storage is mounted to /data_fire if you need to flash anything in CWM copy it to /data_fire/media/0/ as CWM does not see the ext4 usb storage
I've also included a revert script (REVERT_MountSDCARDtoUSB.zip) to undo the changes in case something doesn't work. Just flash with CWM.
If you have issues check/post the output of /storage/usb/moutUSB.log
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-flash this zip after right after.
Change log:
Update 2014/11/18 - v3.1 - Recommended Added KhoaTon's fix for drives with a LABEL set. See post 163 in this thread for details.
Update 2014/11/03 - v3.0 - All versions now mount by UUID. Synced all version numbers. Fixed bug in MountMediaToUSB. MAKE SURE THAT ONLY YOUR DRIVE YOU WANT AS DATA IS PLUGGED IN WHEN YOU FLASH v3.0 zip THAT IS WHEN THE UUID IS READ.
MountPartialDataToUSB_v1.0.zip [For usb thumb drives or Hard drives] Same as MountDataToUSB_v2.5 except it leaves /data/misc /data/system and /data/data mounted to internal storage. See notes above for specifics.
MountMediaToUSB_v1.0zip [For usb thumb drives or Hard drives] - Mounts only /data/media to the USB drive. Should should keep most of everything at normal speed, and expand /data/meda and /sdcard storage. This is where OBB files for games are usually stored.
MountDataToUSB_v2.5.zip [For external hard drives ONLY]- Same as v2 except re-named zip to MountDataToUSB.zip and re-named script and log file to "mountUSB.sh" an "mountUSB.log". Also fixed permission on /data_fire/media/0 so it's easier to push files directly to it for flashing in CWM. Fixed bug with /data/media/0/0 folder.
v2.MountSDCARDtoUSB.zip - (originally posted on page 3) mounts everything except for /data/misc to the usb storage
REVERT_MountSDCARDtoUSB. - Flash this to revert back to normal.
Click to expand...
Click to collapse

jmandawg said:
I DO NOT RECOMMEND ATTEMPTING THIS UNLESS YOU ARE FAMILIAR WITH THE COMMAND LINE
Click to expand...
Click to collapse
I would also highly recommend making sure your recovery is working

good point

This is exactly what Ive been waiting for.. I want to attach a 1TB USB drive to my Fire and just call it a day. I dont even care about storing movies on it or anything.. I pull from my NAS and that has 12TB in it. I just want to be able to install as many apps as I want without running out of room.
I hope this finds its way into the AFTV Tool.. Im too lazy to do this on my own. When you do this kind of crap 50-60 hours a week, reading the forums is about as much as I want to do with computers when I get home.
Anyway, thank you for your hard work! Thats awesome!

so this essentially allows apps to be installed directly onto an external without using apps to foldermount :good:

Nice work.

This method works like a champ. I did a fresh install and started with the basic items i needed. After that, copied the files over to my usb, and finished the rest.
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Not sure why this isnt more visible on the front page. Great work!

t3ch42 said:
This method works like a champ. I did a fresh install and started with the basic items i needed. After that, copied the files over to my usb, and finished the rest.
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Not sure why this isnt more visible on the front page. Great work!
Click to expand...
Click to collapse
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-copy over the install-recovery-3.sh script and add the line to start it back into /etc/init.bueller.sh.
Maybe I will put those 2 things into an update.zip when the next rom is release.

jmandawg said:
Just be aware if you update the firetv image with one of rbox's pre-rooted roms you have to re-copy over the install-recovery-3.sh script and add the line to start it back into /etc/init.bueller.sh.
Maybe I will put those 2 things into an update.zip when the next rom is release.
Click to expand...
Click to collapse
You should really just need to rename it install-recovery.sh.

rbox said:
You should really just need to rename it install-recovery.sh.
Click to expand...
Click to collapse
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.

jmandawg said:
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.
Click to expand...
Click to collapse
Oh I see, the original instructions included editing the init. I thought you were using the mechanism that was in the install-recovery that came from supersu.

rbox said:
Oh I see, the original instructions included editing the init. I thought you were using the mechanism that was in the install-recovery that came from supersu.
Click to expand...
Click to collapse
LOL, yeah, I originally tried that, hence the file name "install-recovery-3.sh" Maybe someone can clean this up and package it, it's a lot cleaner than trying to use stickmount/link2sd.

jmandawg said:
From my experience, It won't work, that script is called too late and sometimes not at all. But feel free to prove me wrong, once i got it working i kinda left it as it was.
Click to expand...
Click to collapse
I can attest to this in some degree. Prior to editing the bueller?.init file, i attempted to just call the script as i was hesitant to modify a system init script. It didnt work.
But then again, i was using scriptmanager to do so. Like the OP, when i got it working, i called it quits.
Maybe there are ways to make this a little less dangerous, but I've only got a single firetv and having it out of commision for a while would be bad...
Thanks again to everybody that works on it. Without the rooted fw, the firetv wouldn't be as cool.

t3ch42 said:
I can attest to this in some degree. Prior to editing the bueller?.init file, i attempted to just call the script as i was hesitant to modify a system init script. It didnt work.
But then again, i was using scriptmanager to do so. Like the OP, when i got it working, i called it quits.
Maybe there are ways to make this a little less dangerous, but I've only got a single firetv and having it out of commision for a while would be bad...
Thanks again to everybody that works on it. Without the rooted fw, the firetv wouldn't be as cool.
Click to expand...
Click to collapse
It's not really dangerous at all, if the script doesn't detect your drive (sda) after 30 seconds it will boot as normal. Also with rbox's CWM Recovery there is nothing to worry about.
It's only dangerous if you fudge up the bueller init script... that might be bad.

Lol, thats the dangerous part i mean. I messed up my init script on my pogoplug, had to get out the serial cable to fix it.
I'd like to keep it accessible with software if I can.
But, like you said, even if the init script gets broken, a backup is easy to recover from. Not as bad as the pogoplug at all.

LOL, i used to have a pogoplug too and a dockstar, i guess i still do but i don't use them anymore. You right, once something doesn't work you have to rip it apart and get out the serial... I ended up getting a chromebox loaded it up with linux and never looked back.

Really, as long as the kernel starts, the sysrq method will get you to recovery. And then from there you can fix anything wrong with the file.

Hey guys,
Any ideas how much space I need on my external drive? I wonder if I can use 16Gb flash drive...
Thanks.

gerikss said:
Hey guys,
Any ideas how much space I need on my external drive? I wonder if I can use 16Gb flash drive...
Thanks.
Click to expand...
Click to collapse
Well the /data partition on the firetv is 5gb... so... if the point is to give you more space... i'd say anything over 5.

rbox said:
Well the /data partition on the firetv is 5gb... so... if the point is to give you more space... i'd say anything over 5.
Click to expand...
Click to collapse
Thanks for the quick reply! The reason I am asking because of this reply:
t3ch42 said:
I have 29gb space showing up in my storage and have no errors or problems with operating. This is a great way to bypass the 5.45gb of free space on a firetv.
Click to expand...
Click to collapse
So if original free space is 5.45Gb and he got 29Gb - looks like he moved around 24Gb... Is my math wrong somewhere?

[TUTO] Enable Adoptable Storage on MM

MM bring the ability to devices which support it to share SD card with system to install apps on SD card. But Sony disabled this on MM. Here is to Enable this functionality
(Be aware that your shared partition will be hidden on other devices)
You will need adb installed on your computer
If you doesn't have it :
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Then connect your phone with adb debugging enabled.
Type "adb shell"
Once you're connected to your device : "sm list-disks"
This will return the ID of your sd card.
Now, if you want the whole sd card to be shared type "sm partition disk:ID private"
If you want your sd to be partitionned type "sm partition disk:ID mixed:%"
(replace ID with your own card ID and % with the STANDARD stockage percent you want on your sd card)
You're done !
(Sizes of partitions are not reported as they should but it seems to work)
Before/After
Before :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After :
Source :
mocado.com
This is Mocado's work, not mine !

But they are testing it on S7 ........ anyone tried on our Sony?

@Elfeno
Is it possible to take and save screenshot after enabling adoptable storage and moved app with this way?
I couldn't access to internal storage in some apps when I enabled adoptable storage with other way (xposed)...

I have successfully done this and everything seems to work fine however when I migrate my data to the SD card so this becomes the default location for new apps and data, I get a memory error in the stock camera app. Is anyone else getting this issue? I haven't yet figured a way around it. This is the one and only issue but it would be a deal breaker

@AndroPlus Since this functionality is part of Android and the 2 memory become one It should not have this issue but will try @roland101 This issue happened to me also after upgrading to MM. Did a clean install wiping data resolved this issue

Hi @Elfeno. I tried a factory reset from the Backup and Restore menu but I still have the issue. How exactly did you do it? Did you already have the SD card private partitioned and data migrated when you did the factory reset? I did, but then my phone didn't recognize the SD card anyway so I had to re-apply the private partition via adoptable storage. I then check the camera, no error. I then migrated all data from internal to SD card from the storage section but after that and a reboot I still get the memory error in the camera app. What were your steps exactly? Thanks

Hello @roland101,
I met the same issue like you. But if your SD card is large enough (like 128GB), you can format it in mixed 25 (reserve 32GB standard storage, other some other value), and then you can use camera on that partition. But the new problem will be: Google Photos(if you use that for backup) cannot delete device copy on that partition (I dont't know why Google Photos didn't request external SD card permission).

@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
About the Google Photos app I guess it store photos in app data and if we cannot write that partition it doesn't allow us to delete these files but should work using Google photo app since it's is own files. If Gphoto was baked with your rom maybe it have arlready the permision needed. You can also check in per apps permissions in settings Check if it delete the cloud backup when you delete local photo.

@Elfeno
Another problem is even get camera to work with a mixed partition. all apps externally calling camera to take photos are dead (like hangout/ telegram)

Elfeno said:
@roland101 @fqj1994 Yes the partition created for apps cannot be use to store files. Mixed will create 1 partition for apps and 1 for files
Click to expand...
Click to collapse
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.

Not sure it worked
fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
Just tried this on a xperia z5 compact and the commands worked the sm partition returned in a few second, little too quick.
When I go into storage i just see a nagative number for both the internal and sd card.
a df from the adb shell shows the below
Filesystem Size Used Free Blksize
/dev 889.4M 96.0K 889.3M 4096
/sys/fs/cgroup 889.4M 0.0K 889.4M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt 889.4M 0.0K 889.4M 4096
/tmp 889.4M 4.0K 889.4M 4096
/system 4.9G 3.8G 1.1G 4096
/data 22.6G 5.0G 17.6G 4096
/oem 290.6M 117.6M 173.0M 4096
/cache 192.8M 260.0K 192.6M 4096
/persist 27.5M 804.0K 26.7M 4096
/firmware 80.0M 56.4M 23.5M 16384
/lta-label 11.7M 1.5M 10.2M 4096
/idd 14.0M 149.0K 13.8M 1024
/rca 8.4M 579.0K 7.8M 1024
/storage 889.4M 0.0K 889.4M 4096
/mnt/runtime/default/emulated: Permission denied
/storage/emulated 22.6G 5.0G 17.6G 4096
/mnt/runtime/read/emulated: Permission denied
/mnt/runtime/write/emulated: Permission denied
/mnt/expand/f9e6c33e-fc2c-45c4-ac57-c6f40d9360d3 117.2G 60.0M 117.1G 4096
is this right 22GB for /storage/emulated ? I would have though it should have been approx 160GB (32+128 - used space)

Actually it's right.
Adoptive storage does not merge two partitions. Or removing sd card will completely disable all installed application of your phone rather than a partial. It just provide ability to Store applications and application data to external storage without applications-aware. And the in the storage settings. You can use migrate data to point which storage to be used for data stored on /sdcard.

Hello,
It work perfectly, but because the function is not officially supported by Sony, displayed size informations are quite strange

fqj1994 said:
Actually it can be used to store files, just go to the adoptive sd card, and click "migrate data", then the adoptive sd card will be mounted to /sdcard, and then Camera will have problems.
Click to expand...
Click to collapse
I am now a little confused. I have a 64GB SD card and originally plan to use the entire SD card for Adoptable Storage.
Based on what's said above, does it make a difference if I choose to
1) partition the SD card to 32GB data+ 32GB for Adoptable Storage, or
2) use the entire SD card for Adoptable Storage?

Seems that it doesnt make any difference !

How I can return my phone to normal can not recognize other memories sd

For me it worked, no problem with stock camera.
Spotify did bug out a little (offline songs were stored to SD card), but a reinstall fixed it. Ii had nothing else set to SD card to begin with anyway.
Thanks for the tip! although I did have to use the whole SD card as private, using it partially would cause popups of new SD-card inserted constantly >> starting to use it would wipe the entire SD.
Using the following firmware:
KPN Mobile NL (32.1.A.1.185 / R3C)

It didn't work =/
Hi I did it all corecly, set the 64gb sd card full private... and started to install many apps... what happend is after it reached the full 16 gb(real internal storage) it would not let me instaling anything else it would just say memory full any one had this?
PS. didn't had any problem with the camera our any other app.

Also applicable on Z3?
Is this workaround also applicable on the z3 with marshmallow

Guys is it Z5c only or applicable on Z3 too?
please help.