Related
In short:
Is there a thread somewhere stating the pro's and con's of running Android from different types of "media" (SD, NAND, EXT2)?
If there is, please provide a link, I can't seem to find anything that isn't an unanswered question or small comments.
If there isn't, let this be a starting point for those looking for the answer to this question.
Longer:
I've seen this question pop up once and again but it might be that the topic is totally exhausted and people have stopped commenting on it. I can't seem to find an answer though; What are the pro's and con's of using NAND, EXT2, FAT32 or any combination of it?
I see a couple of installation alternatives and some I have been able to conclude myself but others not.
* Running from SD-card using HaRET
This option is the slowest in terms of Android performance. It has the added value of easily getting back to Windows Mobile by rebooting the phone, gaining easy access to the SD card and manipulation options.
* Running the system AND data on NAND
This option has in my view the fastest Android experience. Access to files on the SD card is a bit more cumbersome (there is the SD card split widget APK available but I have yet to see it working) and access to files for manipulation I can't comment on (haven't gotten to that yet).
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
* Running the system AND data from EXT2
I have not tried this yet and cannot comment on it. Something tells me it will be slower than NAND because of SD card overhead.
* Running the system from EXT2 and data on NAND
I have not tried this yet and cannot comment on it.
Now, I've missed out on several of the installation options but I'll edit this post as soon as I get to investigating it further.
Any comments/experience/knowledge in this is greatly appreciated, as it can make things clearer as to what options to choose.
Well these are very good question and wanted to start a thread on this matter as well. I also could not find a strait answer anywhere.
I also want to know if there is an advantage using ext2 over fat32.
So, people out there having knowledge about this matter please share it.
Ext2 and Fat32 are both types of filesystem used on various different types of media, including SD card, Hard drives etc.
EXT2 is (one) of the native linux filesystems, and is fully supported in kernel, and is usually faster and more stable in that OS
FAT32 is the 32bit version of the old MSdos filesystem, used up to Windows 98, and still supported by windows machines, but slower and less stable than the native NTFS filesystem used by XP and above.
Nand is actually the type of flash ROM used by our devices, and not a filesystem as such, and running Android in Nand refers to where the information is stored, rather than the filesystem used to store it.
It's equally valid to say that we run WM in Nand also.
I think that in the case of Android EXT2 should be faster and more stable than fat32 since it's designed for Linux, and works better in that OS.
Zenity ik would like to thank you very much as this answers mij questions.
And i think this would many others aswell.
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Thank you all!
Thank you all for commenting! I will add your comments to the Android-wiki I'm building as this question could come back repeatedly from newcomers (and old ones who forgot )!
boli99 said:
Don't forget - if you format your MicroSD to just EXT2 then you will make it very awkward to transfer files to/from the card on a Microsoft Windows based system.
This may, or may not be a problem for you.
Ultimately, the current ideal situation (IMHO) is to run your OS from NAND, and to store your data (music / movies / documents) on a FAT32 format MicroSD - as this enables you to swap the MicroSD card without turning off the device, and provides best cross-platform usability of the MicroSD for the purposes of transferring data to/from it.
Click to expand...
Click to collapse
There is a program for allowing the mounting of EXT2 file systems on windows, however they are not signed. This is more problematic in Windows that are 64bit. The program is called 'ext2fsd' and you can get it from source forge. EXT2 is a better file system, and does not have the 4GB file size limit, and does not fragment (although on a SD card, this should not be an issue). EXT2 also has file permissions that Linux understands. Fat32 has no Access control file permissions.
I have just recently got polymod's eclair running with both system and data on ext2 partitions.
my question is...
I am just wondering what the boot order is...
and where(if possible) can it be changed?
system.img in the andboot folder VS system on partition.
I know it can be set in the installer. but lets say I had installed system on ext2 partition. and then later placed a system.img in the andboot folder.
can I swap between the two?
OK...
I figured it out myself,
You can use the installer to select boot options (Not just options to install)
so I have a system and data on partitons. (currently using)
and I also have a second build installed to .img files in the andboot folder. (for failsafe backup)
if I want to swap from one into the other
I enter installer and change the settings for the system and data to
their respective locations and then just QUIT.
I also still have a donut build in the android folder. as well as still running winmo.
quad boot system on my phone...LOL
Now thats a neat use of the installer, I think this find deserves it's own thread in fact, I'm certain others will find it useful
Tanks !
binlabin said:
* Running the system from NAND and data on EXT2
The performance seems almost as fast as the system+data on NAND. I have no idea about the added value of running anything from an EXT2-partition in the SD card but I'm guessing it will be slower. I have no idea if file access for manipulation is easier or not compared to the other options.
Click to expand...
Click to collapse
I've done some tries with this doing the partitioning from within android and then formatting the FAT32 partition from Windows 7 but the FAT32 partition doesn't work very well afterward. Really slow and sometimes crashes the explorer. Propably something to do with my SD-card. May try doing the partitioning and formatting from Linux to see if it works better.
Seems to me the main advantage of this option is to increase the size of available data storage which i suspect can become a limitation sooner or later in a pure NAND install.
EDIT: Now I've done it and gone NAND-System + EXT2-Data... Partitioned the SD-card from Ubuntu with gparted. Resized the FAT32 partition and created 3 primary EXT2 partitions. only the second (partition 3) should be used though with the setup I am using. It's charging right now so I haven't tried it out much yet but I will later on. However I noticed that I now have 171Mb free phone storage instead of 30-something that I had before (same apps installed).
EDIT2: Ran gparted again and shrinked the unused partition (partition 2) and expanded the data partition (partition 3) so I now have 369Mb free "Internal phone storage". Haven't noticed any speed differences between this and when I had data on NAND.
nand
By then one question:
If im install android in the NAND is more fast ready? But this process erase WM6?
Because now android work good in my HTC TYNT II but the camera and bluetooth not work and have one or two performance problems and for this dont like delete WM6 of my phone, and for this im use Android from my SD.
But look the NAND option because have a problems with the time live of my battery only lasts 5hours with android and SD.
Thanks for your help and cooperation
excellent thread which answers some questions that I had. Thanks to everyone who contributed. The only question remaining though and I have posted this elsewhere without getting an answer:
I partitioned a 2 gb sdcard with ~1.6gb Fat32 and the rest as a single Ext2. I selected system on nand and data on ext2 in the installer. After installation, it does show alot more memory for data as compared to data on nand, BUT I also have a data.img in andboot which is in the Fat32 partition, with a size around 250mb. The question is, is the data in that file or on ext2? If I backup data from installer, it creates a databackup.img in andboot with the same size as data.img. Seems to me the ext2 partition is just taking up space and not being used. Can anyone more knowledgeable shed some light on this? Thanks.
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
zenity said:
Not quite sure what is going on there, seems very counter-intuitive, I would have assumed that system on Nand, data on EXT2 would have installed the data partition to EXT2 on SD. This would seem not to be the case in this instance.
There are a few experiments you could try, if you are brave enough, since you may cause problems by trying any of these suggestions, which could mean a reinstall, I leave it to your judgement how to proceed
Ok firstly I assume you have a card reader, since you managed to partition and format the SD card in the first place. Remove the SD card, insert in card reader, delete the andboot folder, or the contents of the folder, ( may be wise to have a spare SD with either a winmo or android install handy at this point, just in case things go horribly wrong ).
Now with the cleaned SD, put it in the phone and boot, it should boot fine, IF the data is truly on the EXT2 partition.
That at least will answer one question, namely, where the heck is my data?
If this works fine, then I'd just put it down to some inner weirdness of android on non-native devices, if it fails then I'm wondering if your EXT2 partition may have problems, forcing the phone to dump it on the first available good partition, namely the FAT32 one.
Oh and if it does fail, you will have to reinstall, since your data will be toast.
Finally, good luck, I await with interest
Click to expand...
Click to collapse
Great idea, I'll try this on the weekend. I wont delete data though, I'll just rename andboot and backup data for good measure, because I want to be able to go back to the data by renaming it back if it doesn't work. I was also thinking if there is any way to get to the ext2 partition and read it... I'm on xp so I cant do it on my pc, and on the phone, I've looked around in astro n other file managers but cant see anything. But if the case is as golfnz34me points out, then I should just backup the data, and change the option to Fat32 in install and restore data. That should do the trick.
golfnz34me said:
As I recall, the install has the FAT32/Ext2 options incorrectly swapped. It has been this way for a while.
Click to expand...
Click to collapse
Thanks, will check this out. If its true, then great, more speed for my /data! I wonder how I missed this, been going through these forums regularly...
Ok I checked it out, and golfnz34me is correct it seems.
But now I found a new problem. I backed up data, and in the installer, set the data to SDCard, and tried to restore data. It gives various errors like
Code:
cannot determine filesystem size
failed
failed to format
...some other lines...
losetup: /dev/block/loop2: no such device or address
I created the partition with Paragon partition manager, and after getting this error I rechecked in PPM. I reformated the partition, but still get the error. In PPM the partition drive letter isnt assigned. Or, the partition isnt the active partition. Can one of those be the problem? The volume name is Ext2. Im not very experienced in partitioning etc, apart from normal ntfs partition for new hds in windows, so I didnt play with any options. I dont have a linux system either. Any got any ideas? Any help would be appreciated alot!
Not sure about using partition managers other than gparted, afaik most people are using the Gparted live cd if they don't have a linux install handy.
The errors all point to some sort of problem with the EXT2 partition, or it's formatting.
Also EXT2 partitions do not have drive letters, nor do they have to be active partitions.
Apps and data on SD card.
I cant seem to figure out how to make all the apps and other stuff install to the SD card. Do I have to partition the card into two partitions? or is there a way to install the system to Nand and make all the apps and data go to the SD card? Ive tried setting it to System on nand and data on SD partition but it says no partitions to install to or something.
I recently have been reading about the EMMC corruption encountered when flashing ROMs with an ICS based kernels. I've been flashing the different leaked ICS ROMs since they started being leaked and have never paid any attention to the EMMC corruption issue. I've never had any trouble flashing the different leaked ROMs and my phone has always worked fine. However, after reading about this issue I decided to see if I was affected. Problem is I have no idea how to tell for sure if I am. My phone shows the following total capacities:
System storage: 1.92GB
USB storage: 11.50GB
SD card 29.71GB
What I don't quite understand is that my phone has a total of 16GB built-in storage capacity. I'm assuming that System storage accounts for 2GB. That would leave 14GB left for USB storage? Concern is that there is only 11.50GB of storage which means that there is 2.50GB of storage missing and/or has been effected by EMMC corruption???
OR
USB storage is only 12GB instead of 14GB and the remaining 2GB that appears to be missing isn't really missing but rather some sort of reserved system storage that the system uses and I can't touch? If this is the case then I presume that I've probably been very very lucky and somehow not fallen victim to the EMMC corruption that others have?
Does anyone know the answer to my concern?
Not another of thesr threads. Use custom kernels by agat or chris41g and you will mot brick. Simple as that!
Sent from my SPH-D710 using xda premium
There is an entire thread (or two) here about the eMMC issue. And another sticky about how not to brick your device. Take the time to read them.
Chainfire has an application which can tell you if your firmware is susceptible here http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 I will bet it is.
SO if you are going to flash anything use the latest safe kernel from Agat and Chris41g. They have removed the offending code from the newly relesed kernel source.
Goog luck.
StoverA said:
Does anyone know the answer to my concern?
Click to expand...
Click to collapse
You don't have the issue. Your 16GB is being used as internal SD, /data partition, /system partition, /cache partition
Also when you format, you lose capacity for the filesystem metastructures.
You will know quite easily if you have the problem. If you factory reset, it will start hanging and if you try and flash a full rom it will hang on data.img or factoryfs.img.
BTW it isn't corruption in the sense that the filesystem locks out bad sectors. It is corruption in the sense that whenever the bad sectors are accessed, even just to scan for bad sectors, the phone completely locks up.
Thank you Sfhub.
sfhub said:
You don't have the issue. Your 16GB is being used as internal SD, /data partition, /system partition, /cache partition
Also when you format, you lose capacity for the filesystem metastructures.
You will know quite easily if you have the problem. If you factory reset, it will start hanging and if you try and flash a full rom it will hang on data.img or factoryfs.img.
BTW it isn't corruption in the sense that the filesystem locks out bad sectors. It is corruption in the sense that whenever the bad sectors are accessed, even just to scan for bad sectors, the phone completely locks up.
Click to expand...
Click to collapse
Thank you for answering my question. I could not account for the missing 2GB of storage and now I know where it is. Until yesterday I had not bothered to read anything about the EMMC issue. Then I spent most the evening reading about the issue and have concluded that I have been extremely fortunate. I think I have flashed every ICS leaked build that has been leaked.
I was however not careless. For starters, I used only sfhub's leaked ICS stock rooted builds. And I've used only Agat and Chris41g based kernels. Additionally I used a specific process each time I installed a new leaked ICS build.
Thank you Sfhub for all the work that you do. I am a big fan of yours and appreciate you. Additionally, I want to also Thank Agat and Chris41g for their work as well. These three are a huge asset to the Epic 4G Touch community!
Hi,
I know this properly have been asked many times ind here before, but I hope someone can help me out anyway.
To solve the classic problem with "low memory", I tried to root and install CM7 to my phone. Which I did manged to do, also more then just one time. But I allways run into the memory problem later on. So I read a few more threads, which said that I just use S2E and A2SD together. I even installed A2SDGUI.
But know matter what I do, I allways sees the problem with "low memory" eventually, perhaps 4 months later perhaps sooner. To my understanding, this should not be a problem, when you use S2E and A2SD scripts. Which make me think that I haven't done it right.
So my wish is that someone can give me a detailed manual to follow, so I can get past the f...... memory problem, and especially how to test to se if it works.
My SD Card is a Samsung 16GB class 10 card. I know your not excited about class 10 cards, but I'l give it a go, and I'llthink I have a smaller class 8 at home.
I like CM7, but as CM is my first and only custom rom I have tried, I can't say I don't like the others. So I'm not bound to any version, I just want to get the newest possible version of Android, which is fully functioning.
Hope someone can and will help.
Pick any ROM you want, open the .zip file, go to /system/etc/init.d/ and delete the 10apps2sd script (it can be named like this or something very similiar), if there is no a2sd built then it's even better - dont do anything.
Now download - http://d-h.st/1vK , place it on the root of sdcard.
Wipe everything, make sure you have 1-1.5GB ext3 or ext4 partition (i suggest 1GB)
Flash the ROM, and then without leaving recovery flash the above a2sd script. ( http://d-h.st/1vK )
Voila, done you have 1 - 1.5GB internal memory. (depending on how big you ext partition is)
Keep in mind this script will keep all kind of app data on SD, so it might be slower (most a2sd scripts keeps /data/ partition on internal memory for performance reasons)
But since you're looking for a unlimited space it should fit you.
If you dont know how to flash a ROM, or ROOT then you need to read some flashing guides first.
Well I would like both when some app are on the internal memory, and other on the sd card. Cause some apps don't work well, when on sd card. So if there are a way to make this happen, it would be great. But that isn't the case is it?
Any I coming to try this.
It seems to be working, but when I through Titanium Backup restore a game (Big Business), I can't start that. It begins to load, and the switch back to startscreen. Then it switchs back and forth, before it eventually stops the game.
Is that because the backup is from another setup, with a2sd's?
Try to remove the application data and try again.
Nope, that didn't help
Hello everyone,
I know I'm pretty new here but I have been digging these forums for a few days right now.
I recently bought a faster 16 GB SD Card and rooted my phone to install bigger and other ROM.
But I found verry little info (maybe I didn't looked has much or at the right place) about the swap space you can create in your sd card.
What I read was that it was usefull for the system but when I look at the differents ROM thread they never or very rarely talk about a needed swap place in the sd card partitioning.
Right now I created an ext4 partition with a little bit more than 1gb and a swap with +- 400 mb.
So my question is, is it really usefull or no?
ps: sorry for my english
Gil- said:
Hello everyone,
I know I'm pretty new here but I have been digging these forums for a few days right now.
I recently bought a faster 16 GB SD Card and rooted my phone to install bigger and other ROM.
But I found verry little info (maybe I didn't looked has much or at the right place) about the swap space you can create in your sd card.
What I read was that it was usefull for the system but when I look at the differents ROM thread they never or very rarely talk about a needed swap place in the sd card partitioning.
Right now I created an ext4 partition with a little bit more than 1gb and a swap with +- 400 mb.
So my question is, is it really usefull or no?
ps: sorry for my english
Click to expand...
Click to collapse
As far as I know, there are vrey few ROMs that require swap partition. It is usually requested in the first post of the ROM's thread.
Ciobby said:
As far as I know, there are vrey few ROMs that require swap partition. It is usually requested in the first post of the ROM's thread.
Click to expand...
Click to collapse
Ok, thanks !
I will re create my sd card then
Well after a few rom tested I'm not so sure about this...
Ok they never talk about swap space. But the general problem I have when I install a big rom with Android 4.x is that the memory is always full.
Therefore the phone becomes extremly slow when I launch a few applications.
The only solution I found is to install an app to manage the RAM and free some space. But even with this, I need more ram as it's almost alway full.
I will try with a swap of 512 Mo but I have no idea how other people can manage this.
If anyone have a tip about this, it would be great .
Gil- said:
Well after a few rom tested I'm not so sure about this...
Ok they never talk about swap space. But the general problem I have when I install a big rom with Android 4.x is that the memory is always full.
Therefore the phone becomes extremly slow when I launch a few applications.
The only solution I found is to install an app to manage the RAM and free some space. But even with this, I need more ram as it's almost alway full.
I will try with a swap of 512 Mo but I have no idea how other people can manage this.
If anyone have a tip about this, it would be great .
Click to expand...
Click to collapse
If you use the native a2sd scripts that come with 4.x ROMs, then that's your problem. Those scripts only move data/app to sd-ext, leaving the rest on internal. Most of the memory is occupied by dalvik cache.
This script should also move dalvik to ext. Try it.
http://db.tt/m4sQLDOI
Don't forget to backup first.
I never used a swap partition. I think there's no need for it.
abaaaabbbb63 said:
If you use the native a2sd scripts that come with 4.x ROMs, then that's your problem. Those scripts only move data/app to sd-ext, leaving the rest on internal. Most of the memory is occupied by dalvik cache.
This script should also move dalvik to ext. Try it.
http://db.tt/m4sQLDOI
Don't forget to backup first.
I never used a swap partition. I think there's no need for it.
Click to expand...
Click to collapse
Thanks for your anwser but right now I'm using this rom:
http://forum.xda-developers.com/showthread.php?t=2213033
And I already moved dalvik and data to sd in the installation. I tried every option there, only data, only dalvik and both. Only both is working.
But this doesn't change the RAM used (or maybe it's not so important that the RAM becomes full?)
I also tried other 4.x rom and moved everything but at some point I think there is too many info in the ram and the Desire becomes really laggy.
Gil- said:
Thanks for your anwser but right now I'm using this rom:
http://forum.xda-developers.com/showthread.php?t=2213033
And I already moved dalvik and data to sd in the installation. I tried every option there, only data, only dalvik and both. Only both is working.
But this doesn't change the RAM used (or maybe it's not so important that the RAM becomes full?)
I also tried other 4.x rom and moved everything but at some point I think there is too many info in the ram and the Desire becomes really laggy.
Click to expand...
Click to collapse
creating a 512MB swap partition is pretty much useless as most ROMs don't implement it. It's a redundant partition which could either be used as extra sd-ext for apps or FAT32 space for music etc. It can cause problems as well depending on the order of partitions.
Even if somehow it could be used, it won't suddenly turn the desire into a phone with 1GB RAM...that's not the way it works. In cases where it is used, only a small swap partition ~25-32MB to occasionally swap a few things in and out of memory. Even then whether it actually makes a difference is dubious imo.
I would recommend repartitioning from scratch again, remove the swap partition. You don't need it, and the ROM you're running won't recognise it's even there.
It's laggy not only because of RAM, and can't be solved by magically adding more of it . Android memory works differently as well, so free RAM is wasted RAM, you shouldn't have to monitor how much is free at any given time. A big part of the lag is simply because it's a JB ROM which is simply very resource heavy on the desire relative to GB ones.
eddiehk6 said:
creating a 512MB swap partition is pretty much useless as most ROMs don't implement it. It's a redundant partition which could either be used as extra sd-ext for apps or FAT32 space for music etc. It can cause problems as well depending on the order of partitions.
Even if somehow it could be used, it won't suddenly turn the desire into a phone with 1GB RAM...that's not the way it works. In cases where it is used, only a small swap partition ~25-32MB to occasionally swap a few things in and out of memory. Even then whether it actually makes a difference is dubious imo.
I would recommend repartitioning from scratch again, remove the swap partition. You don't need it, and the ROM you're running won't recognise it's even there.
It's laggy not only because of RAM, and can't be solved by magically adding more of it . Android memory works differently as well, so free RAM is wasted RAM, you shouldn't have to monitor how much is free at any given time. A big part of the lag is simply because it's a JB ROM which is simply very resource heavy on the desire relative to GB ones.
Click to expand...
Click to collapse
Thanks for the informations.
Right now I only have an Ext4 of 1 Gb + 15 gb in Fat32. I didn't had the time to recreate the partitions again. So won't do it.
Well I thought it was a RAM issue because without the ram manager app some functions becomes hard to load like.
If I receive a call the phone rings but wait some time before loading the info to display about the call.
Or if I want to answer an sms the keyboard takes time to load.
Same thing with the apps.
With the ram manager it generally loads faster but some time it gets buggy because there is too much work to do to free space (I suppose).
Well that leave me not alot of options about the capacities of the phone .
Maybe just go back to 2.3.x
total memory 5.7 gb ?
why?
boramat said:
total memory 5.7 gb ?
why?
Click to expand...
Click to collapse
What total memory? is it rooted? on a custom rom? have you installed any apps? more info would be nice
Rayx Revive said:
What total memory? is it rooted? on a custom rom? have you installed any apps? more info would be nice
Click to expand...
Click to collapse
total internal sd card memory
rooted
custom rom
i installed apps but all memory so free and used memory total 5.7 gb
then system or rom using abut 9 gb???
boramat said:
total internal sd card memory
rooted
custom rom
i installed apps but all memory so free and used memory total 5.7 gb
then system or rom using abut 9 gb???
Click to expand...
Click to collapse
The first thing u need to know is that if you are using a Rom based on the samsungs rom, then it takes around 4-5gb (i.e they say 16gig, but dont mention 6gb rom)
If you shift to a CM based rom you'll have 12-13 gb free.
But, if you want to clear memory, you can use folder mount to shift the data of bigger games to to your external sd card
boramat said:
total memory 5.7 gb ?
why?
Click to expand...
Click to collapse
Because you screwed it up. Total memory should be around 10 GB. You probably repartitioned it for whatever reason. Before you do anything else to it, figure out what you did and how you can restore it back to the normal partition structure.
sputnik767 said:
Because you screwed it up. Total memory should be around 10 GB. You probably repartitioned it for whatever reason. Before you do anything else to it, figure out what you did and how you can restore it back to the normal partition structure.
Click to expand...
Click to collapse
i bought 3 days ago
i just rooted and installed custom rom
boramat said:
i bought 3 days ago
i just rooted and installed custom rom
Click to expand...
Click to collapse
None of that changes what I wrote. But I do find it funny how you refuse to take responsibility.
To recap, you bought a tablet that has around 10 GB of total memory available at time of purchase, you then completely modified the system to something other than what it shipped with, and now you are wondering why you have roughly half of the available memory. You screwed it up somewhere between 3 days ago and today.
Your question should not be "why I only have 5.7 GB of memory" but rather "how do I revert the tablet completely back to stock and restore the partition table." Unfortunately I can't help you here, but there are plenty people here who can. But the simple answer to your original question is that you did something that caused half of your memory to be unavailable. I would be lying if I told you that I've never had this happen to other Android devices that I've owned, but the reason for it was always of my own doing.
Start a new thread along the lines of "I messed up flashing ROMs and now only have 5.7 GB free," and ask for advice on how to restore the tablet back to stock. You will probably need a pit file and use ODIN. Make sure you specify the exact model number of your device, exactly what and how you flashed, and only flash ROMs that are specifically made for your device. Or even better, just keep it stock rooted.
And for future reference, it would behoove you to give as much information as you possibly can, when you come here with a problem. When it started, what you did, how you did it, how you tried to fix it, etc. Unfortunately, if all you tell me is "I have only 5.7 GB free, why?" all I can tell you is that you messed it up. Most of us don't like to fish for necessary information, which is probably why you didn't get too many responses.
sputnik767 said:
None of that changes what I wrote. But I do find it funny how you refuse to take responsibility.
To recap, you bought a tablet that has around 10 GB of total memory available at time of purchase, you then completely modified the system to something other than what it shipped with, and now you are wondering why you have roughly half of the available memory. You screwed it up somewhere between 3 days ago and today.
Your question should not be "why I only have 5.7 GB of memory" but rather "how do I revert the tablet completely back to stock and restore the partition table." Unfortunately I can't help you here, but there are plenty people here who can. But the simple answer to your original question is that you did something that caused half of your memory to be unavailable. I would be lying if I told you that I've never had this happen to other Android devices that I've owned, but the reason for it was always of my own doing.
Start a new thread along the lines of "I messed up flashing ROMs and now only have 5.7 GB free," and ask for advice on how to restore the tablet back to stock. You will probably need a pit file and use ODIN. Make sure you specify the exact model number of your device, exactly what and how you flashed, and only flash ROMs that are specifically made for your device. Or even better, just keep it stock rooted.
And for future reference, it would behoove you to give as much information as you possibly can, when you come here with a problem. When it started, what you did, how you did it, how you tried to fix it, etc. Unfortunately, if all you tell me is "I have only 5.7 GB free, why?" all I can tell you is that you messed it up. Most of us don't like to fish for necessary information, which is probably why you didn't get too many responses.
Click to expand...
Click to collapse
at the beginning my device had just 5.7-6 gb storage total
but about 3 gb samsung films and musics , my deviced display product but anyone dont touch before, it is new
i erased samsung films and music
rooted and installed stock rooted rom
but i have 5.7 gb still
im loking by advanced partition data, 15 gb total storage but mmcblk10 has 2800 mb and mmcblk1 has 1910 mb storage and they are hidden
i m not seing
boramat said:
at the beginning my device had just 5.7-6 gb storage total
but about 3 gb samsung films and musics , my deviced display product but anyone dont touch before, it is new
i erased samsung films and music
rooted and installed stock rooted rom
but i have 5.7 gb still
im loking by advanced partition data, 15 gb total storage but mmcblk10 has 2800 mb and mmcblk1 has 1910 mb storage and they are hidden
i m not seing
Click to expand...
Click to collapse
Ok, this is what I mean by telling you to provide as much info as you can at the start. All of this would be great (absolutely necessary) to know at the very beginning. You installed stock rooted rom, did you use ODIN (a lot of things can go wrong if used incorrectly)? I'm guessing that you did, but did you accidentally repartition? Is the ROM specific for your device and region? And you are saying that the brand new device had only 5.7 GB available storage or total storage. Either way, I still maintain that there is something wrong with your partition table.
My partition table is as follows:
mmcblk0: 15028.0
mmcblk0p9: /system 2519.8
mmcblk0p12: /data 10110.5
mmcblk1: seems to refer to my SD card, 30436.5
Those are the main relevant ones. There are other small portions. I used the app called partition table to pull this info. My device is wifi-only 16 GB.