Database Users

[Q] Cannot Format /Data

Whenever I try to format /data through CWM 3.0.2.8, it returns the message.
error while formatting /data
Click to expand...
Click to collapse
Also when I try to restore a backup, CWM cannot format /data.
I've also tried to install CM7. It says it completed its install in CWM but when I reboot, it retains the OS (rooted stock 1.2) I was currently on.

Me too. I just updated to MR1 and I am trying to restore the /data directory and I can't.

There's one thing I noticed about this refurb'd nook color. The space available in the device info is 1GB. Shouldn't it be higher or did they change the file structure with the latest models?
Also, I went into ADB and mounted EMMC. The last modified date for the files in there is May 4th.
Edit
Not sure if this would help.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 1 9 72261 c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LB
A)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LB
A)
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7937MB 7477MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
(parted)
Click to expand...
Click to collapse

Someone responded back to me on this forum.
http://androidforums.com/b-n-nookcolor/333668-format-internal-partition.html#post2672750
Barnes & Noble has started shipping new NOOK Color devices that are partitioned to allow only 1 GB of "user sideloaded" storage. The remaining 7 GB are partitioned for the OS, apps from the new B&N Apps store, and items downloaded directly from B&N. For the typical (non-rooted) device, the user would have to use the microSD slot for additional storage. I suspect you got one of the newly partitioned devices, which is why you are now seeing only 1 GB instead of the previous 5 GB of storage available.
Click to expand...
Click to collapse
Is there anyway to repartition the new devices or I'm stuck with this? If not, it's going to prevent me from dualbooting. This might also be the cause of my second problem, installing CM7 and still ending up with the original OS.

Oh man am I glad I found this thread. I was freakin' out when I couldn't load phiremod onto my newly purchased NC. Turns out I can only see 1GB of storage like the others in this thread. Hopefully some one will find a way to repartition the newer devices otherwise I am stuck with a rooted NC running the stock ROM with no way to return it.

You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.

jb7038 said:
You can just "Reset to factory default" and it'll remove the root. Then you can try to return it or exchange it. I'd probably say this if they ask for a reason...
"It's showing 1GB space as opposed to 8GB space as advertised"
Though I'm wondering why install CM7 doesn't change anything. After installation, it still boots up the stock OS.
Click to expand...
Click to collapse
Trying to load new ROMS fails because I can't do a data wipe as instructed.

I wonder if they made it so that outside sources can't write or modify /data now but it's still rootable with manualnooter.. I can format the other partitions through CWM and restore them easily.
EDIT
http://www.barnesandnoble.com/nookcolor/features/index.asp?cds2Pid=35583
*1GB = 1 billion bytes; Actual formatted capacity may be less. Approximately 5GB available to store content, of which up to 4GB may be reserved for content purchased from the Barnes & Noble NOOK Store.

I am not sure what kind of security they could have on the actual partitions, but the dual boot ROMS show that resizing the partitions should not be to hard, though it does mean you may lose data (possibly).

I don't mind losing my /data. I rather be able to install CM7 or something on the EMMC as opposed to running it on the SD.
I'd be grateful if someone could show me how to partition it so it's back to the original partition, 4gb/4gb as opposed to 7gb/1gb I think.

I hope something is figured out soon.

Here's the solution to anyone following this thread.
http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110

I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....

Sparks1641 said:
I had this problem too.. bought a brand new nook color... this is what i did using CWM 3.0.2.8 to boot off SD...
1. used manual nooter 4.5.6
(after applying had all types of popup force close messages about /media this /media that)
2. changed my patitions to match this post
http://forum.xda-developers.com/showpost.php?p=13003431&postcount=166
(Note: Although it said that it didnt write the partitions it actually did)
3. did the 8 boot reset and nook button reset...
(This didn't reset the partitions actually and I had 5.sumthin GB free space not 1GB as before)
4. Manual nooted again then installed Phiremod 6.2 and Dalingrin's Kernel 042411 for cm7....
Click to expand...
Click to collapse
I did this too and it scared the crap out of me when it kicked me out of fdisk. I thought I hosed it for good. Then when I did the 8 resets it kept going into CWM on the 8th reset. It wasn't until I rebooted it from CWM did it go and reflash itself.
Man that was scary. I thought I had a $250 paper weight.

I was a little freaked out when the fdisk said it didn't work... But reading around I seen that its almost impossible to break it as long as you don't mess with the first 3 partitions so what was the worse case I figured... This must be an issue with the CWR though.. Probably just updating the CWR to format different sizes of the partitions... A format with offset and length feature in an advanced menu... then we can change the sizes to what we want.. But going forward until CWR gets updated every new nook probably gonna have to do the partition change... Not like that's a big deal...

I bought a Nook Color used off craigslist cus they "bricked" it. I thought, no prob, through in the CWM uSD card, erase the data and system, and throw 1.2 on to root.
Can't erase the Data!
They said it was only a few weeks old. I'm guessing it was a refurb with new partition, they tried to root it somehow, and messed it up, then gave up.
Let's hope this fixes it!

Let us know if the partition thing works.. that would be cool.. GL.....

Sparks1641 said:
Let us know if the partition thing works.. that would be cool.. GL.....
Click to expand...
Click to collapse
I did the repartition here:
http://forum.xda-developers.com/showthread.php?t=1094371
and it worked like a charm - finally have CM7 on my 4th Nook!
Thanks to DeanGibson.

[Q] How do I partition the eMMC to support Custom ROMs?

I bought my NC last week and immediately rooted it with out a hitch using ManualNooter for stock 1.2. In the process of trying to flash Phiremod my NC locked up in CWM when doing a wipe data/factory reset as instructed. I did a hard reset and tried to load Phiremod any way, which failed. I ended up using the backup I made of the rooted clean stock OS and it is working.
I read this thread
http://forum.xda-developers.com/showthread.php?t=1077973
and mine has the same issue of a partitioned eMMC that only reports 1GB. This prevents me from loading custom ROMs and side loading any applications.
One of the posts on that last thread mentions how dual booting essentially repartitions your eMMC to allow for the said dual booting, so I tried the "Step 1" in the repartition process here...
http://forum.xda-developers.com/showthread.php?t=959461
And it failed, but did boot back into my stock rooted OS.
My question is...
Is there a way to repartition my NC with what seems to be a new partition scheme that B&N moved to so that I can load custom ROMs, sideload programs, and/or dual boot off of eMMC?

Would like to see this answered as well.

grab your oars....
I'm in the same boat.... I have the 1 gig partition on my new Nook.
I can boot from SD ok but I would rather blow out the stock and save my SD.
Help?
MBK

Anyone out there can help us repartition the newer nooks?

side load partition 1 gb on newer NC's
guys check this out. I am doing it now and will report back after I get this done.
http://forum.xda-developers.com/showthread.php?t=914690
boot repartition with stock 1.0.0 or 1.0.1, then side load 1.2 update from b&n site:
http://www.barnesandnoble.com/u/nookcolor-support-software-update/379002520/
If I read all this correctly.. this should do the trick. as well as re-enabling apk installs correctly with rooted stock?

Already tried that.
You'll get a 1.0.0 or 1.0.1 with 0 Space available and you cannot sideload because of that. All that does is re-write the folders and not partition it.
I even tried changing the factory.zip with an older version in the /emmc and did a system/data wipe through the 8 boot fails and power + n reset.

One possibility
jb7038 said:
Anyone out there can help us repartition the newer nooks?
Click to expand...
Click to collapse
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.

I'm just unfamiliar with the block sizes and the commands to partition/change it.
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
Click to expand...
Click to collapse
6 938MB 6490MB 5552MB logical ext3
7 6490MB 6860MB 370MB logical ext3
8 6860MB 7937MB 1077MB logical fat32 lba
Click to expand...
Click to collapse
____________________________________________
I do have the NC I'm suppose to send back that's fully wiped.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
~ #
Click to expand...
Click to collapse
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
(parted)
Click to expand...
Click to collapse
I'd be willing to partition it myself before I send it back if someone could walk me through it.

DeanGibson said:
If you are familiar with fdisk and mkfs.ext2 or are willing to learn, and can boot a rooted OS from the SDcard, it should be trivial to delete, resize, repartition, and reformat /data (0p6 -- ext3), /cache (0p7 -- ext3) and /media (0p8 -- vfat). Do note the size of the partitions (especially 0p7/cache) before deleting them.
Then, when you restart the NC, it should recreate the contents of /data and /media to virgin content (meaning you better have backed up any non-B&N content). You will have to reregister with B&N, so you should probably do this on an UNROOTED Nook.
This is an experiment that I have wanted to try, but have not had the time; I've been too busy doing other experiments, like having B&N do the intentional repartitioning. I was using internal dual boot before, but uninstalled it before the repartitioning, because I knew there would not be enough space for dual boot afterwards.
Click to expand...
Click to collapse
Dear God I would love to try but honestly I don't know a think about command line linux. Also, mine is already rooted, but I can always take it back to stock.
If someone gets this to work please document the process. I would really like to be able to use the internal memory for custom ROMs and be able to side load programs.

Anyone that can help us?

Best Partition Scheme?

I'm looking for some input into what you fine folks think is the best partition scheme for the Kindle Fire. Share yours, constructively criticize others; this is a battle royale in which the winner will get my KF partitioned under his or her scheme.

6/7GB and then the rest for the OS. Only because yesterday I tried to transfer all my Amazon MP3 bought stuff using doubleTwist and 5GB wasn't enough and didn't give me room for anything else. :silly: 1GB is enough for the OS.

Jessical said:
6/7GB and then the rest for the OS. Only because yesterday I tried to transfer all my Amazon MP3 bought stuff using doubleTwist and 5GB wasn't enough and didn't give me room for anything else. :silly: 1GB is enough for the OS.
Click to expand...
Click to collapse
Isn't this the default?

moore.bryan said:
Isn't this the default?
Click to expand...
Click to collapse
I think that's his point.
Sent from my DROID3 using xda app-developers app

No, it's 5GB.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

So, it seems, the forum has answered one of two options:
the ROM's native partition is fine or
increase the sdcard partition by 1GB.
About right?

Jessical said:
No, it's 5GB.
Click to expand...
Click to collapse
It looks like I misunderstand the Fire's memory partitioning..
When I look at the partitioning my Fire running CM9 nightly's from Hashcode, I see its got 528mb for System ROM (281 free), 1.17Gb Internal (975 mb free) and 5.36Gb for the SDcard partition. I thought that layout was standard. That's more than 5Gb for the SDCard though, right ?
Adding that up I get only about 7Gb accounted for, so I am for sure missing something. Recovery partition for TWRP maybe ?
I got these numbers from Titanium Backup Pro, so maybe its not telling me stuff I don't need to know about.
You are saying you can increase the SDCard partition from 5.36Gb to 6Gb by reducing the size of the Internal partition ?
If so, would that limit the number and size of the programs you could install on your Fire, but give you more room for music and stuff ?
Thanks,
Glenn

glennj99 said:
It looks like I misunderstand the Fire's memory partitioning..
When I look at the partitioning my my Fire running CM9 nightly's from Hashcode, I see its got 528mb for System ROM (281 free), 1.17Gb Internal (975 mb free) and 5.36Gb for the SDcard partition. I thought that layout was standard. That's more than 5Gb for the SDCard though, right ?
Adding that up I get only about 7Gb accounted for, so I am for sure missing something. Recovery partition for TWRP maybe ?
I got these numbers from Titanium Backup Pro, so maybe its not telling me stuff I don't need to know about.
You are saying you can increase the SDCard partition from 5.36Gb to 6Gb by reducing the size of the Internal partition ?
If so, would that limit the number and size of the programs you could install on your Fire, but give you more room for music and stuff ?
Thanks,
Glenn
Click to expand...
Click to collapse
I'm running Jelly Bean and it says my internal is 1.09GB, and then my internal SD is 5GB. I'm getting that from the Settings page...
It wouldn't limits the number of programs, but you'd probably have to push them to the SD card for storage (some apps already do that though). But yeah, it'd give you more space for media too.

Are you using this Jelly build?

moore.bryan said:
Are you using this Jelly build?
Click to expand...
Click to collapse
Yep.

Jessical said:
Yep.
Click to expand...
Click to collapse
I tried it, briefly, and jumped ship because it didn't auto-rotate from landscape to portrait. I check the thread, also briefly, but didn't see anyone reporting the same. Am I missing something?

Code:
Model: MMC MMC08G (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 525kB 512B
4 525kB 525kB 512B
5 525kB 16.9MB 16.4MB recovery
6 16.9MB 16.9MB 512B
7 16.9MB 25.1MB 8191kB boot
8 25.1MB 25.1MB 512B
9 25.1MB 537MB 512MB ext4 system
10 537MB 1561MB 1024MB ext4 userdata
11 1561MB 1817MB 256MB ext4 cache
12 1817MB 2841MB 1024MB fat32 media msftres
13 2841MB 7818MB 4977MB ext4 linux
Of course I have nearly 5gb dedicated to linux, but that space can be used for media.
/thread

What makes you think this is the best way? Not being difficult, just trying to understand the inner workings...

Samsung Galaxy tab 2 7.0 Capacity

Today i bought a Samsung galaxy tab 2 7.0 8 GB, it is using Android 4.0.3, i was looking at the specs of the tablet and i noticed that the Device memory shows 4.59 GB available and it shows 275 used RAM and 410 free RAM for a total of 687 RAM, when it should be 8 GB of device memory and 1 GB of RAM, i went back to the store to ask what was the deal, and they couldnt answer, since it was already late at night they werent able to contact Samsung techs, they say that most likely its a 4GB tablet and that Samsung made a mistake advertising the table(which i doubt), could this problem be because of the ROM?? or most likely a factory problem? because im having my doubts now, i been going all night on google, and i find that it should be 8 GB or device memory and 1 GB of RAM, has anyone had this problem before? im going to contact the store and samsung tomorrow and see what the problem is, hope its a factory problem or ROM problem.

pahb22 said:
Today i bought a Samsung galaxy tab 2 7.0 8 GB, it is using Android 4.0.3, i was looking at the specs of the tablet and i noticed that the Device memory shows 4.59 GB available and it shows 275 used RAM and 410 free RAM for a total of 687 RAM, when it should be 8 GB of device memory and 1 GB of RAM, i went back to the store to ask what was the deal, and they couldnt answer, since it was already late at night they werent able to contact Samsung techs, they say that most likely its a 4GB tablet and that Samsung made a mistake advertising the table(which i doubt), could this problem be because of the ROM?? or most likely a factory problem? because im having my doubts now, i been going all night on google, and i find that it should be 8 GB or device memory and 1 GB of RAM, has anyone had this problem before? im going to contact the store and samsung tomorrow and see what the problem is, hope its a factory problem or ROM problem.
Click to expand...
Click to collapse
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 343M 76K 343M 4096
/mnt/asec 343M 0K 343M 4096
/mnt/obb 343M 0K 343M 4096
/system 1G 972M 405M 4096
/data 4G 1G 2G 4096 <- 4 Go
/cache 688M 11M 677M 4096
/efs 19M 4M 15M 4096
/mnt/sdcard 4G 1G 2G 4096 <- 4 Go
/mnt/extSdCard 14G 7G 7G 4096 <- my external sdcard (16 gb)
Same as you, I don't really like the way how this is partionned.
/data should be 8 go and /mnt/sdcard should be the real external sdcard...

fbl0droid said:
[email protected]:/ $ df
Filesystem Size Used Free Blksize
/dev 343M 76K 343M 4096
/mnt/asec 343M 0K 343M 4096
/mnt/obb 343M 0K 343M 4096
/system 1G 972M 405M 4096
/data 4G 1G 2G 4096
/cache 688M 11M 677M 4096
/efs 19M 4M 15M 4096
/mnt/sdcard 4G 1G 2G 4096
/mnt/extSdCard 14G 7G 7G 4096
Click to expand...
Click to collapse
Thanks for the reply, so from what i can see (if im correct) the tab has 2 partitions? one for sdcard, the one that shows 4.59 GB and i guess the other 4 GB are system, data and the ROM? or am i wrong?

Basically yes , it's reserved for system use. Not much you can do about it either.

Sorry for the reply, can we manage the partition of the system or they are specific size for cache/temp files?
Can we see in memory management all the 1Gb of ram?

Aliendex said:
Sorry for the reply, can we manage the partition of the system or they are specific size for cache/temp files?
Can we see in memory management all the 1Gb of ram?
Click to expand...
Click to collapse
As i know no their is amount of memory and disk size reserved to system to do its functions and to load the operating system from disk and to load important components of operating system to memory after boot the only way to have full disk size and full memory is to format system completely and by this the device will not even boot again will be dead only black screen no operating system to load at all do not try this at home or at school
Sent from my GT-P5100 using xda app-developers app

Mohamedselim said:
As i know no their is amount of memory and disk size reserved to system to do its functions and to load the operating system from disk and to load important components of operating system to memory after boot the only way to have full disk size and full memory is to format system completely and by this the device will not even boot again will be dead only black screen no operating system to load at all do not try this at home or at school
Sent from my GT-P5100 using xda app-developers app
Click to expand...
Click to collapse
And, if I only want to see 1gb ram in settings?
Not 1 Gb for user application, only for see how android manage the system hidden application

Aliendex said:
And, if I only want to see 1gb ram in settings?
Not 1 Gb for user application, only for see how android manage the system hidden application
Click to expand...
Click to collapse
My advice is to leave it alone , It would be very easy to brick the device. How would you recover the settings if it went wrong ? ...... up to you , your device to play with !

Sean_Seany said:
My advice is to leave it alone , It would be very easy to brick the device. How would you recover the settings if it went wrong ? ...... up to you , your device to play with !
Click to expand...
Click to collapse
I know it's dangerous but i think Samsung need to expose a ram management in Settings for see all the 1 Gb
Can anyone know if in the Jelly Bean TEST india we can see al the ram?

Code:
# busybox ls -l /dev/block/platform/omap/omap_hsmmc.1/by-name
lrwxrwxrwx 1 root root 20 Sep 10 04:32 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Sep 10 04:32 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 Sep 10 04:32 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Sep 10 04:32 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Sep 10 04:32 HIDDEN -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Sep 10 04:32 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Sep 10 04:32 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Sep 10 04:32 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Sep 10 04:32 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Sep 10 04:32 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Sep 10 04:32 SBL2 -> /dev/block/mmcblk0p3
16GB version have 516040kB HIDDEN partition for preload contents.

same issues
pahb22 said:
Today i bought a Samsung galaxy tab 2 7.0 8 GB, it is using Android 4.0.3, i was looking at the specs of the tablet and i noticed that the Device memory shows 4.59 GB available and it shows 275 used RAM and 410 free RAM for a total of 687 RAM, when it should be 8 GB of device memory and 1 GB of RAM, i went back to the store to ask what was the deal, and they couldnt answer, since it was already late at night they werent able to contact Samsung techs, they say that most likely its a 4GB tablet and that Samsung made a mistake advertising the table(which i doubt), could this problem be because of the ROM?? or most likely a factory problem? because im having my doubts now, i been going all night on google, and i find that it should be 8 GB or device memory and 1 GB of RAM, has anyone had this problem before? im going to contact the store and samsung tomorrow and see what the problem is, hope its a factory problem or ROM problem.
Click to expand...
Click to collapse
Ya I noticed that to on my 8 gig Galaxy tab 2 7.0 (3113) there is a way to switch external with internal memory in this forum! Say you had a 32 gig SD card you can switch the internal 4gigs for the 32gig external worked for me good!

AW: Samsung Galaxy tab 2 7.0 Capacity
Its the same on all devices, some of the internal memory are for the System,same for the RAM. A nexus 7 16gb have round about 12,5gb free internal memory, i thought that knew everyone
Gesendet von meinem GT-P3110 mit Tapatalk 2

out of 1gb ram...around 200 to 250 mb ram is dedicated for gpu...its the same for devices of all companies!
update to jelly bean and u'll get 774mb ram as opposed to 687mb on ics!

Most devices share the integraded "sdcard" now. Is not a real sdcard like others ( older devices have individual internal storage), just a bigger eMMC which is basicly the same. It is partitioned in various blocks including our internal storage.
About the ram, you will never get over ~820mb of total ram available to use and that is on some cases, very few of them, on a 1gb ram device. Back when 512mb devices came out, usually the most we could get was about 200mb.
One very good word of advice. Just use the tablet and forget about how much ram is in use, unless you are having issues. When i got my first android, an HD2, i struggled for free ram. I was always on it but when i bought my first galaxy, i just flashed a good custom rom and forgot about closing apps. Android was taking care of it just nice and i was on froyo back then. I still tell people to not close apps, and uninstall task managers, also any antivirus (useless stuff). They do nothing. A task manager is another application running. Hope is good for you.
Cheers.
Sent from my GT-P3113 using xda premium

[Q] Resizing /system and /cache to gain space?

Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?

I3ig Al said:
Hello everyone and thank you for having me on your wonderful forum. I have learned so much in such a short time by reading everything I could whether I was intending to use it or not.
I got my 16gb Nexus on Monday and immediately prepped it for ROMs, settling on CM10.1 RC2, Prior to that I had an Optimus V running CM7. On my Optimus, after flashing CM7 for the long haul I was able to move all excess /system space back into /data using terminal emulator and the fdisk command, but I followed a guide of some sort that is long lost now.
Everything is fantastic so far except one thing, there seems to be quite a lot of space reserved in the /system and /cache partitions, and I am not sure if I am able to re-partition this space back to /data or how exactly to do this.
right now /system is reading at 395.8 / 827.8 MB used, and /cache is at 68.4 / 551.7 MB. I would like to repartition 200 MB away from /system and 300-400 MB away from /cache, and put it back into /data. This will leave me some space to integrate or convert a few apps to system apps, and enough cache space to be safe (why does it need 550 MB to begin with?) and give back another half gig of storage that I paid so much to have.
I have three issues with this, one being that I can find almost no information on this topic directly mentioning the NExus 4, and any relatable information from other devices talking about device specific toolkits to do the job.
The only thread I found on XDA about this is below, and it only gave me a vague "this is not possible"
http://forum.xda-developers.com/showthread.php?t=2248400
The second issue is I do not recall the command switches/flags that go with the fdisk command, only that I had to use some things to set file permissions or remount the partition or some such (I know, i'm a noob, forgive me).
Lastly, I am rather confused by the multiple partitions of /data and /storage/emulated all showing a partition size of 13231.8 MB. Obviously they are all the same physical space, but I am afraid to mess with the partitions and break what I assume are a ton of symlinks that trick apps into believing there is an external SD card in play. Can any of you shed some light on this for me?
Click to expand...
Click to collapse
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything

75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.

I like this. The only "issue" is that if more space were ever to be reallocated to /system or /cache, it'd require wiping /data obviously. Small price to pay. 500MB isn't too small a chunk for 8GB users.

75markus said:
nexus4 doesn´t have a fix size for partitions, you can use the whole memory for everything... no need to re-partition anything
Click to expand...
Click to collapse
Actually it does. System data cache and boot, plus like 30 other ones, same as any other phone with no micro SD card
Sent from my Nexus 7 @1.60 GHz on Stock 4.2.2

I3ig Al said:
I'm not sure if you are misunderstanding or not reading my whole post, or if I am not understanding you or the situation I am posting about, so please don't take offense to this reply.
It appears to me that the /system partition is reserving 827 MB space for the ROM, and CM10.1 is only using 400 MB of it
It also appears that 552 MB is reserved for the /cache partition, and only 70 MB is being currently used.
This is ~900 MB of storage space that is reserved and unused. I would like to know if it is possible to reallocate ~500-600 MB of this back into the /data partition for user space.
Please explain to me how this space is part of the whole memory that can be used for anything.
After posting I have thought some more about it and decided to NOT mess with the partition sizes, mainly because I do not know what effect it would have if I were to flash another ROM in the future, which is almost a given when Key Lime Pie is released. However I would still like to understand what I have asked about in case I do want to do this in the future, and also just for the sake of expanding my knowledge.
Click to expand...
Click to collapse
i think N4 uses FUSE (Filesystem in Userspace) file system
noobdeagle said:
isnt this what they were saying was the reason for no SD card and use of MTP ?; basically if i recall correctly the nexus devices do not truly assign partitions instead there is a storage 'pool' that anything can use dynamically.
so i guess there is no partitions its just all 1 volume.
source: http://www.androidcentral.com/why-nexus-devices-have-no-sd-card
Click to expand...
Click to collapse

That is for the sdcard.
The other partitions such as /system still have fixed amounts of space allocated
Sent from my Nexus 4 using xda app-developers app