Database Info

[Q] Low Space Warning

Has anyone else run into a situation where your tablet has received a low space warning on your Transformer but you haven't installed/used a lot of space?
When I look at my storage break down I use about 400mb of media and 12GB+ of application. When I view by application there is no way that it's 12GB. So I installed DiskUsage and the "system data" is using 11GB on it's own. I am suspecting it some how related to system crashes but have not confirmed this. Anyone else?

I am having the same problem just different amount of space shown

I've been digging around in adb tonight trying to get to the bottom of this:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
/system 503M 340M 163M 4096
/data 13G 11G 1G 4096
/cache 521M 8M 512M 4096
/mnt/sdcard 13G 11G 1G 4096
I've been trying to get a good look into /data, but it's a system owned directory and you need root access to view some of the contents.
When I try to run:
adb shell ls /data
It responds:
opendir failed, Permission denied
Looks like I will have to root to continue the hunt, because I want to find the cause. The unfortunate thing is I need to revert my version back to 8.3.2.9 to be able to perform the root successfully. About to begin work on that now.

Is it when you are updating apps in the market and the app installation fails with a low space warning?
My Nexus S does that (with over 6gb available), then re-try the install and it works. Not sure where the issue is.

@tekkitan my big concern is:
Code:
/data 13G 11G 1G 4096
/mnt/sdcard 13G 11G 1G 4096
Because I've only used about 500MB's of space.
But you are correct I get the error trying to install from the market, and sometime if I delete some apps I can make enough room to install a new one.
There is a difference between 2.x and 3.x of android and how it allot's space for apps. In 2.x there is a partition that is limited size where you can install apps no matter the size of the onboard memory, unless you root and work around it. In 3.x they changed that and all free space can be used for apps.

So I can't perform the root tonight, I don't have a microSD card I can use to downgrade to 8.2.3.9. Will have to wait until tomorrow now.

wildbohr said:
@tekkitan my big concern is:
Code:
/data 13G 11G 1G 4096
/mnt/sdcard 13G 11G 1G 4096
Because I've only used about 500MB's of space.
But you are correct I get the error trying to install from the market, and sometime if I delete some apps I can make enough room to install a new one.
There is a difference between 2.x and 3.x of android and how it allot's space for apps. In 2.x there is a partition that is limited size where you can install apps no matter the size of the onboard memory, unless you root and work around it. In 3.x they changed that and all free space can be used for apps.
Click to expand...
Click to collapse
The Nexus S only has internal storage so it is similar.
Did you try just re-trying the download instead of removing apps? Like I said, if I just simply retry the isntallation/update, it works just fine.

I can't get imagine how apps could significantly impact the internal memory on a 16 or 32gb TF.
I've been loading apps on my Droid X internal 8gb memory with wild abandon for almost a year, and have only used up about 3gb. Tablet scaled apps might be somwhat larger, of course, but not that big.
Sent from my DROIDX using Tapatalk

Again I don't think it is a space issue. Just a bug with the Android Market.

[Q] Insufficient Storage Available

ASUS Transformer -- Latest version of Revolver, using v22a of supercurios kernal, and the ice cream sandwich theme, v2.
I've searched and searched, bu haven't found a case similar to mine.
When trying to download and install or update apps, I always get a notification saying that there was "insufficient storage available".
I have over 3 gigs free on the Internal memory, and nearly 6 on my microsd card.
I've read about people wiping or deleting items in the dalvik cache, and I've read about clearing market data.
My problem is, some say that wiping the dalvik cache on custom roms can break them, requiring a new flash.
I also have another problem. Nearly 100% of the time, downloads fail in the stock browser. I'm not sure if they fail in other browsers, but frankly I don't care-- I haven't come across a single browser in the market that I actually like. Most aren't even worth the megabytes they eat up.
And I also can't get over the fact that one of androids nucest features of all times, the move apps to SD card function, is unavailable to me. This makes my 80 dollar high-speed microsd card that I bought specifically for fast application use useless.
What can I do about either issue? The app update and install and the storage issue is a priority for me.

I would be interested in what the output of 'df -hPa' is on your system (in the terminal).
Sent from my Transformer TF101 using Tapatalk

yup, i get that as well at times, it really is annoying however, a reboot normally always fixes it and a wiping of any and all caches (from recovery) will keep that problem from coming back for a long time. I always make backups (once a week) so that if I wipe the cache wrong or something, I can restore from the recovery backup I made. I havent had to reflash a rom yet (crosses fingers)

Spidey01 said:
I would be interested in what the output of 'df -hPa' is on your system (in the terminal).
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Spidey.. got this today driving me mad..
here is my output in terminal..
'df -hPa' = Filesystem 1k-blocks Used Available Use% Mounted on df: hPa: can't find mount point.
ok.. whats this telling me?
I have wiped cache's
un-installed a couple of big programs/games..
TB is reporting that I have the following..
System rom: 528MB(127MB Free)
Internal 13.3GB(8.51GB Free)
SD card 13.3GB(8.51GB Free)
settings/storage is showing..
12.43GB with 7.93GB free..
I undocked it, rebooted it..
pulled out the SDcard and tried to install..
but no joy..
looks like maybe a reinstall of the Rom, then slowly load things back in..
edits: looks like a mounting problem.. as the dock is not mounting usb1 for the external now..
will flash Blades kernel and see if it sets things right..
as the only difference in my set-up has been to flash Roachs kernel during the week..
a Kernel flash didn't fix it so am doing a full reset...
K..after a full Factory/data reset..
TB give me this now.. (Market loaded a few in.. but I stopped it.. )
System rom: 528MB(108MB Free)
Internal 13.3GB(9.08GB Free)
SD card 13.3GB(9.08GB Free)
settings/storage is showing..
12.43GB with 8.46GB free..
Will load TB backup back in and see if the problem starts again..
But If I have had this problem.. I am sure others will come across it..
as it seems I got a corrupted file somewhere in there,
will keep an eye on it and see if it happens again..
but for sure, there was a corrupt system file..
Anyone know which are the actual system files are called for the mounting operation?

**** happened again today..
after a clean install.. ran well yesterday..
this morning plugged in the USB Drive into the right USB and had a USB mouse in the left USB..
wonder if this is doing something to mount files?
Anyone know which are the actual system files are called for the mounting operation?
I might run with just the sdcard for the rest of the week shifting things on to it..
and see if I am getting a spike, hooking up with the usbdrive that is corrupting mounting files..
as this would seem like the problem.. its a western digital 500g portable that I am plugin and unpluggin

I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.

romified said:
I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.
Click to expand...
Click to collapse
I wouldn't mind knowing how.. incase I need to do it..
mine has settled this week as not been plugging/unplugging in the USB hard-drive..
so I have narrowed it down to this spike corrupting some files..
I have backed up the system/lib files incase I have to dump them back over top of corrupted ones.. as it will save a new Rom Flash..
as still not had time to narrow down the actual file or files needed for Mounting USB's in the Rom
If you could post here or PM.. would be grateful..

Basically you just use nvflash to flash a ROM, I flashed Prime since there was a nvflash version available.
All you have to do is edit the flash.cfg file in nvflash, and make the following change, and your system partition will go from 512mb to 768mb. I was trying to port a large ROM and kept running out of space, I made this change and never had a space issue since.
REMEMBER: nvflash will wipe all of your files and data, recovery and kernel as well. So make sure whatever you flash with nvflash is what you want in place. You can of course always reflash through regular CWM to any rom as well after using nvflash. You just need to flash something with nvflash to make the partition changes. And remember if you use nvflash in the future, if you do not edit the flash.cfg file per below, nvflash will partiton system back to 512mb when you use it.
It is only one line, so this is VERY easy. I have only tested this on a TF101-A1. I am not sure what the 32 GB (B1) models partition layout is like.
Open the flash.cfg file, and look for this (it started on line 93 of the flash.cfg I have):
Code:
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=536870912
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
Change the "size=536870912" to "size=805306368" and save the file. The above section should now look like this :
Code:
[partition]
name=APP
id=9
type=data
allocation_policy=sequential
filesystem_type=basic
size=805306368
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=system.img
Now use nvflash as normal and your system partition will be 768mb.
I am not sure what the limit is on size or what else can be changed, so if you test, do so at your own risk, I have only changed system to 768mb. I think partition 16 is elastic and sizes based on space left over from other partitions (so this is where the extra space for system comes from), but I am not 100% sure on this yet. But do let us know if you do experiment as to what you learn
By the way, the "805306368" number is a number calculated based on bytes & cylinders (or something along those lines) :
1024 x 1024 (1048576) x size in mb = size used in above example
ie: 1048576 x 768 = 805306368

dgcruzing said:
'df -hPa' = Filesystem 1k-blocks Used Available Use% Mounted on df: hPa: can't find mount point.
Click to expand...
Click to collapse
Maybe a typo or damaged mount point? /system, /data, and /cache are what matters.
Code:
Thank you for using Better Terminal Emulator Pro
/ $ df --help
BusyBox v1.16.2androidbtep (2011-08-11 14:16:08 PDT) multi-call binary.
Usage: df [-Pkmhai] [-B SIZE] [FILESYSTEM]...
Print filesystem usage statistics
Options:
-P POSIX output format
-k 1024-byte blocks (default)
-m 1M-byte blocks
-h Human readable (e.g. 1K 243M 2G)
-a Show all filesystems
-i Inodes
-B SIZE Blocksize
/ $ df -Pha
Filesystem Size Used Available Capacity Mounted on
tmpfs 364.2M 32.0K 364.2M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
debugfs 0 0 0 0% /sys/kernel/debug
none 0 0 0 0% /acct
tmpfs 364.2M 0 364.2M 0% /mnt/asec
tmpfs 364.2M 0 364.2M 0% /mnt/obb
none 0 0 0 0% /dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /system
/dev/block/mmcblk0p7 27.3G 4.1G 23.3G 15% /data
/dev/block/mmcblk0p2 512.8M 16.0M 496.8M 3% /cache
tmpfs 364.2M 0 364.2M 0% /Removable
/dev/fuse 27.3G 4.1G 23.3G 15% /mnt/sdcard
tmpfs 364.2M 32.0K 364.2M 0% /data/local/mnt/Linux/dev
devpts 0 0 0 0% /data/local/mnt/Linux/dev/pts
proc 0 0 0 0% /data/local/mnt/Linux/proc
sysfs 0 0 0 0% /data/local/mnt/Linux/sys
debugfs 0 0 0 0% /data/local/mnt/Linux/sys/kernel/debug
none 0 0 0 0% /data/local/mnt/Linux/acct
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/mnt/asec
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/mnt/obb
none 0 0 0 0% /data/local/mnt/Linux/dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /data/local/mnt/Linux/system
/dev/block/mmcblk0p7 27.3G 4.1G 23.3G 15% /data/local/mnt/Linux/data
/dev/block/mmcblk0p2 512.8M 16.0M 496.8M 3% /data/local/mnt/Linux/cache
tmpfs 364.2M 0 364.2M 0% /data/local/mnt/Linux/Removable
/dev/fuse 27.3G 4.1G 23.3G 15% /data/local/mnt/Linux/mnt/sdcard
/ $
The other stuff you posted makes sense to me, as long as you have a 16GB TF and not a 32GB like mine.
The /data/local/mnt/Linux stuff is because of my Debian chroot, and the sdcard is really a cool hack they do for mounting /data/media correctly for Android. The mmcblk devices are the partitions on the internal memory, as far as I know at least.
Applications go in /data. Your /system partition can be touched by some things but you are not generally going to be stuffing apps in there when you go to the market. You can make an app a system app with some program I think but I wouldn't reccomend it for most apps without good reason.
As root, you can see for yourself with ls what is in the file system and see how Android does stuff, it's mostly self explanitory with some poking but not as obvious as people like me (or smarter people on the subject) might think.
Idk how the file system performance would be impacted here with regards to free space, I know FreeBSD with classic UFS2 / UFS2+SU on PCs will suffer heavy performance issues if the file system is tooooo full but now I'm talking Apples and Oranges. But I would be curious how increasing the /system partition would work for performance with the TF's specifics.
Sent from my Transformer TF101 using Tapatalk

Re: Transformer 16g system partition hack
Well after having it happen again to me today, I decided to bite the bullet and spend the night doing Romified's hack..(Thanks)
I nvflashed Prime 1.7 with the adjusted flash.cfg
As a note: using Notepad++ mine was on line 99
Will load it backup and see how we go..
Fingers crossed this will settle it down..
As said before.. once the problem starts.. even wiping programs off doesn't seem to store updates or allow installs of new programs, so it seems that only a good nflash is the way to go..
Will update as the week goes on..
Getting back to the hack..
it is interesting to get in to the Linux partition reading..
As the layout here seems to give us a bit of scope to play with..
I played safe and didn't push it this time..
but.. that's not to say that there couldn't be some decent discussion on
the actual need for so many partitions and their sizes..
This was the Terminal dump before the hack and with a flash of Prime 2.1/Blades latest Kernel.(As tried everything else before going ahead with the Nvflash hack)
Code:
/ # df -Pha
df -Pha
Filesystem Size Used Available Capacity Mounted on
tmpfs 364.2M 32.0K 364.2M 0% /dev
devpts 0 0 0 0% /dev/pts
proc 0 0 0 0% /proc
sysfs 0 0 0 0% /sys
debugfs 0 0 0 0% /sys/kernel/debug
none 0 0 0 0% /acct
tmpfs 364.2M 0 364.2M 0% /mnt/asec
tmpfs 364.2M 0 364.2M 0% /mnt/obb
none 0 0 0 0% /dev/cpuctl
/dev/block/mmcblk0p1 503.9M 403.5M 100.5M 80% /system
/dev/block/mmcblk0p7 12.4G 3.2G 9.2G 26% /data
/dev/block/mmcblk0p2 521.2M 9.1M 512.1M 2% /cache
tmpfs 364.2M 0 364.2M 0% /Removable
/dev/fuse 12.4G 3.2G 9.2G 26% /mnt/sdcard
/dev/block/vold/179:9
14.7G 3.9G 10.8G 27% /Removable/MicroSD
Will post back the new dump once got things loaded and settled..

romified said:
I modded the flash.cfg file in nvflash and increased my system partition from 512mb to 768mb. It works great. If anyone is interested in increasing their system partition size, I can post what I did to do it. You would need to backup your stuff as it wipes everything when you flash the new partitions.
Click to expand...
Click to collapse
This is pointless, /System is a ReadOnly filesystem.

well its back to the drawing board for me as it came back tonight..
after loading a small-iss program of 2meg from the market..
honest this is giving me the ****s..
as internal is showing 2.2g
system is 408mb of 504mb
this is the output on terminal with "df"
Code:
/ $ export PATH=/data/local/bin:$PATH
/ $ df -Pha
Filesystem Size Used Free Blksize
-Pha: No such file or directory
/ $ df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
[COLOR="Red"]/system 503M 407M 96M 4096[/COLOR]
/data 12G 2G 9G 2048
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 2G 9G 2048
/R......./MicroSD 14G 4G 10G 8192
/ $
What is painful is I am clearing cache, going in and wiping programs
not only from market and also internally.. like in private data.. also apps out of system/apps
also wiped Market cache & Data..
but it doesnt seem to free up enough memory to allow even a 160k widget to download then download
an install from market..
Edit: Just did a test.. maybe its nothing to do with the actual Rom build..or Partitions but Market itself..
as I uninstalled a program downloaded from Market using another apps manager..
had a backup of it..
then re: installed it..via Root explorer.. installed no problems.. and is a 12meg program..
K.. will do a few more tests.. maybe its an unstall of market.. or a roll back..

dgcruzing said:
well its back to the drawing board for me as it came back tonight..
after loading a small-iss program of 2meg from the market..
honest this is giving me the ****s..
as internal is showing 2.2g
system is 408mb of 504mb
this is the output on terminal with "df"
/ $ export PATH=/data/local/bin:$PATH
/ $ df -Pha
Filesystem Size Used Free Blksize
-Pha: No such file or directory
/ $ df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
/system 503M 407M 96M 4096
/data 12G 2G 9G 2048
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 2G 9G 2048
/R......./MicroSD 14G 4G 10G 8192
/ $
What is painful is I am clearing cache, going in and wiping programs
not only from market and also internally.. like in private data.. also apps out of system/apps
also wiped Market cache & Data..
but it doesnt seem to free up enough memory to allow even a 160k widget to download then download
an install from market..
Edit: Just did a test.. maybe its nothing to do with the actual Rom build..or Partitions but Market itself..
as I uninstalled a program downloaded from Market using another apps manager..
had a backup of it..
then re: installed it..via Root explorer.. installed no problems.. and is a 12meg program..
K.. will do a few more tests.. maybe its an unstall of market.. or a roll back..
Click to expand...
Click to collapse
try clearing the dalvik cache that may help you

Hi Stevie,
Yes..one of the first things I did..
But to no avail..
I see by your threads that you have a fair knowledge of how the partitions work and file structures work..
Would you know what are all the files associated with market and where all the directries are associated with it..?
I have found market.apk
Market update.apk
But where is market dropping the files you buy?
And market database filed?
At the moment, I am still leaning towards market doing something screwy to me..
As the test with
1:uninstall with root explorer
2:then a reinstall with TB
Proves that I can write to the partition.
But a..
1: uninstall 2 programs- with market
(Which in theory should free space)
2: reinstall 1 program- with market
Gives me the error again..
sent from yet another MikG HTC Evo

Just wondering how much room there is on the TF for apps? Just got one over the weekend...plus I use an N1 that has >200 MB...so from what I've read in this thread so far...seems that you can load up a butt load of apps on this tablet.

dgcruzing said:
Hi Stevie,
Yes..one of the first things I did..
But to no avail..
I see by your threads that you have a fair knowledge of how the partitions work and file structures work..
Would you know what are all the files associated with market and where all the directries are associated with it..?
I have got found market.apk
Market update.apk
But where is market dropping the files you buy?
And market database filed?
At the moment, I am still leaning towards market doing something screwy to me..
As the test with
1:uninstall with root explorer
2:then a reinstall with TB
Proves that I can write to the partition.
But a..
1: uninstall 2 programs- with market
(Which in theory should free space)
2: reinstall 1 program- with market
Gives me the error again..
sent from yet another MikG HTC Evo
Click to expand...
Click to collapse
It should download it to /cache then install it to /data nothing else
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
SiNJiN76 said:
Just wondering how much room there is on the TF for apps? Just got one over the weekend...plus I use an N1 that has >200 MB...so from what I've read in this thread so far...seems that you can load up a butt load of apps on this tablet.
Click to expand...
Click to collapse
because /data and the emmc share the same partition, it is as much as you can store on your tablet, so 14ish GB on a 16GB device and 28ish GB on a 32GB device, unless of course you are running ubuntu in dual boot which shrinks the size of /data

lilstevie said:
It should download it to /cache then install it to /data nothing else
---------- Post added at 12:59 PM ---------- Previous post was at 12:58 PM ----------
because /data and the emmc share the same partition, it is as much as you can store on your tablet, so 14ish GB on a 16GB device and 28ish GB on a 32GB device, unless of course you are running ubuntu in dual boot which shrinks the size of /data
Click to expand...
Click to collapse
Yes, this is what I was figuring too.. that's why its frustrating me to be getting this error and leading me to believe that its a market problem..
I have already ruled out a space problem..
as time permits, I am going to wipe market off and try to install another version and see what happens..
This is why I am in the need of ALL files that point to and are called by market to wipe off it.. so that there are no rouge orphan files around..
Then of course going to have to hunt down a another copy to load in..
which I should be able to pull from one of the Roms..
as I dont want to use the one in Roach's Rom.. as this is the one that is maybe causing problems..(Via some unexplained help from Market update)
Note of course.. that I am not saying that it is anything to do with Roach's Rom and or files in it.. as I am still in the investigation stage of why I am getting the error..

dgcruzing said:
Yes, this is what I was figuring too.. that's why its frustrating me to be getting this error and leading me to believe that its a market problem..
I have already ruled out a space problem..
as time permits, I am going to wipe market off and try to install another version and see what happens..
This is why I am in the need of ALL files that point to and are called by market to wipe off it.. so that there are no rouge orphan files around..
Then of course going to have to hunt down a another copy to load in..
which I should be able to pull from one of the Roms..
as I dont want to use the one in Roach's Rom.. as this is the one that is maybe causing problems..(Via some unexplained help from Market update)
Note of course.. that I am not saying that it is anything to do with Roach's Rom and or files in it.. as I am still in the investigation stage of why I am getting the error..
Click to expand...
Click to collapse
is this on one rom? or has it happened to you on a few, and what rom are you running

lilstevie said:
is this on one rom? or has it happened to you on a few, and what rom are you running
Click to expand...
Click to collapse
Been on Roach's with C& B Kernel.. first time it happened swopped out to Blades Kernel..
Maybe its a Rom swop for a while to see if it settles..
might save the time spent on hunting down the problem..
Got a trip for a few weeks so don't want to be stressed with this on the road..
so got to get it settled in the next few days..
edit: going to run out of time.. as said on the road from Sunday..so decided to go a new Rom flash..
This is how it is looking like at the moment..
Code:
export PATH=/data/local/bin:$PATH:.
/ # export PATH=/data/local/bin:$PATH:.
/ # df
Filesystem Size Used Free Blksize
/dev 364M 32K 364M 4096
/mnt/asec 364M 0K 364M 4096
/mnt/obb 364M 0K 364M 4096
[COLOR="Red"]/system 755M 296M 459M 4096[/COLOR]
/data 12G 1G 10G 4096
/cache 521M 8M 512M 4096
/Removable 364M 0K 364M 4096
/mnt/sdcard 12G 1G 10G 4096
/Removable/MicroSD 14G 4G 9G 8192
/ #
interesting comparing it to the last one posted last night..
I have now got the full 755m in system as per nvflash..
as last one is only showing 503m with most of the same apps loaded back in..
I have done :
Mike1986 super wipe..
Then loaded in KRAKD rom..
Blue theme
Blades CptAwesome 12-07
let see how it goes..

why there is no swap partition on my android device?

free
total used free shared buffers
Mem: 183584 176468 7116 0 8
-/+ buffers: 176460 7124
Swap: 0 0 0
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 91792 12 91780 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock4 174080 155676 18404 89% /system
/dev/block/mtdblock6 194176 69136 125040 36% /data
/dev/block/mtdblock5 71680 1172 70508 2% /cache
/dev/block/mtdblock7 20480 1168 19312 6% /data/HWUserData
/dev/block//vold/179:1
1919304 6320 1912984 0% /sdcard
so can i enable a swap partition to my android device? how to make it?

Use home partition wizard tool
Hope can help you

RudzLong said:
Use home partition wizard tool
Hope can help you
Click to expand...
Click to collapse
so can i create partition using fdisk directly?
the issue is whether the kernel support swap function, agree with that?

bigmeow said:
so can i create partition using fdisk directly?
the issue is whether the kernel support swap function, agree with that?
Click to expand...
Click to collapse
Yes, the kernel supports swapping. But Android do not page swap by design, but kills of entire processes instead. I.e. the "swapping" (memory management) is implemented at application level. Swapping is slow, you'll get at best 20MB/s disk I/O, and Android must be "real time best effort". E.g. if your are playing Angry Birds and have your phone app out-paged, it'll take time to page it back in again, before you can answer your friend calling. It's much quicker to kill of the Angry Bird than have to page it out, especially as the I/O capacity is occupied loading the phone app.
But yes, you can enable paging on the Android device, and it'll probably work quite fine most of the times. But ApplicationManager doesn't really cares, it'll kill of your apps anyway. Running native code although, it'll give you some gain.

kuisma said:
Yes, the kernel supports swapping. But Android do not page swap by design, but kills of entire processes instead. I.e. the "swapping" (memory management) is implemented at application level. Swapping is slow, you'll get at best 20MB/s disk I/O, and Android must be "real time best effort". E.g. if your are playing Angry Birds and have your phone app out-paged, it'll take time to page it back in again, before you can answer your friend calling. It's much quicker to kill of the Angry Bird than have to page it out, especially as the I/O capacity is occupied loading the phone app.
But yes, you can enable paging on the Android device, and it'll probably work quite fine most of the times. But ApplicationManager doesn't really cares, it'll kill of your apps anyway. Running native code although, it'll give you some gain.
Click to expand...
Click to collapse
the issue is how to enable paging?

bigmeow said:
the issue is how to enable paging?
Click to expand...
Click to collapse
Code:
[email protected]:/usr/tmp # free
total used free shared buffers
Mem: 738260 723056 15204 0 78588
-/+ buffers: 644468 93792
Swap: 0 0 0
[email protected]:/usr/tmp # busybox dd bs=1M if=/dev/zero of=swapfile count=256
256+0 records in
256+0 records out
268435456 bytes (256.0MB) copied, 20.161636 seconds, 12.7MB/s
[email protected]:/usr/tmp # busybox mkswap /usr/tmp/swapfile
Setting up swapspace version 1, size = 268431360 bytes
UUID=35fb0d4e-b0ed-4b08-9935-64b85e71d6ce
[email protected]:/usr/tmp # busybox swapon /usr/tmp/swapfile
[email protected]:/usr/tmp # free
total used free shared buffers
Mem: 738260 650516 87744 0 78824
-/+ buffers: 571692 166568
Swap: 262140 0 262140
Change "count=256" to the size (in MB) you want your the swap. Locate the file to your fastest disk, here I'm using /usr/tmp, but I guess you'll have to place it somewhere else, since /usr/tmp usually don't exists in Android. You'll have to use either /data (expensive!) or make a new ext3 partition on your SD card for this (best, if you've got a fast SD card). The swap file can reside on the sdcard, but it must not be on the fat partition, but on an ext3 or ext4 partition.

Unfortunately kernel doesn't allow for that
(Galaxy Note, SpeedMod kernel k-11)
Code:
/sdcard $ dd if=/dev/zero of=swapfile bs=1M count=256
256+0 records in
256+0 records out
268435456 bytes (256.0MB) copied, 31.747960 seconds, 8.1MB/s
/sdcard $ busybox mkswap swapfile
Setting up swapspace version 1, size = 268431360 bytes
/sdcard $ busybox swapon swapfile
swapon: swapfile: Function not implemented
/sdcard $
/sdcard $
Carefully crafted on my Galaxy Note, for your eyes only

debernardis said:
Code:
/sdcard $ busybox swapon swapfile
swapon: swapfile: Function not implemented
Click to expand...
Click to collapse
Try swapping on an ext3/ext4 device, and also use the full file path of the swap file to "busybox swapon".
Edit: Tested. If I try swapping on a FAT disk, I'll get the same error. ext3/4 works like a charm.

kuisma said:
Try swapping on an ext3/ext4 device, and also use the full file path of the swap file to "busybox swapon".
Edit: Tested. If I try swapping on a FAT disk, I'll get the same error. ext3/4 works like a charm.
Click to expand...
Click to collapse
hey dev i read the whole thread n came to the conclusion that my device which is unbranded doesnt have swap support in kernel nor ext3-4 support
i tried swapper 2 with swap file but it shows function not implemented
so i tried to mount ext3 partition but it doesnt mount on the device seems it dont have ext3 support whereas i tried ext2 n mounted successfully but swap file on it still shows function not implemented
it would b nice if u can help me
thanks alot

[Q] Internal SD Card doesn't mount! [i9023]

Hello. Firstly thanks for a helpful forum you guys have made. It has helped me greatly so far.
My SD card doesn't mount.
How it happened:
I installed ClockworkMod Recovery and CyanogenMod 10 (stable).
Upon reboot, I stupidly encrypted the phone.
After that finished, I flashed Marmite kernel (stable), however this slowed down my phone completely.
To revert back, I re-flashed CyanogenMod.
After this reboot, the SD card could not mount.
Info
Parted /dev/block/mmcblk0
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 1612MB 1074MB ext4 userdata
3 1612MB 15.9GB 14.3GB media
In /dev/block the file list is this;
Code:
mmcblk0 (SD Card)
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
This looks like there are perhaps 6 partitions on my SDcard.
In CyanogenMod 10, df command shows;
Code:
Filesystem Size Used
/dev 198.2M 48K
/storage 198.2M OK
/mnt/secure 198.2M OK
/mnt/asec 198.2M OK
/mnt/obb 198.2M OK
/mnt/fuse 198.2M OK
/cache 469.5M 91.5M
/efs 6.8M 5.6M
/system 503.9M 370.3M
/data 1007.9M 145M
Im stuck in how to get this sorted. Every time I got to mount in CWM is states 'Error mounting /sdcard!'
Is it just possible to delete all the partitions in /dev/block for the SDCard?

[solved]
alfanhui said:
Hello. Firstly thanks for a helpful forum you guys have made. It has helped me greatly so far.
My SD card doesn't mount.
How it happened:
I installed ClockworkMod Recovery and CyanogenMod 10 (stable).
Upon reboot, I stupidly encrypted the phone.
After that finished, I flashed Marmite kernel (stable), however this slowed down my phone completely.
To revert back, I re-flashed CyanogenMod.
After this reboot, the SD card could not mount.
Info
Parted /dev/block/mmcblk0
Code:
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB ext4 system
2 538MB 1612MB 1074MB ext4 userdata
3 1612MB 15.9GB 14.3GB media
In /dev/block the file list is this;
Code:
mmcblk0 (SD Card)
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p2
mmcblk0p3
This looks like there are perhaps 6 partitions on my SDcard.
In CyanogenMod 10, df command shows;
Code:
Filesystem Size Used
/dev 198.2M 48K
/storage 198.2M OK
/mnt/secure 198.2M OK
/mnt/asec 198.2M OK
/mnt/obb 198.2M OK
/mnt/fuse 198.2M OK
/cache 469.5M 91.5M
/efs 6.8M 5.6M
/system 503.9M 370.3M
/data 1007.9M 145M
Im stuck in how to get this sorted. Every time I got to mount in CWM is states 'Error mounting /sdcard!'
Is it just possible to delete all the partitions in /dev/block for the SDCard?
Click to expand...
Click to collapse
I have fixed this issue. These are the steps I took;
Download latest factory image; (https://developers.google.com/android/nexus/images)
Boot into bootloader (power and volume up when phone is switched off)
Connect to PC, and make sure you have the fastboot downloaded from android SDK
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
Once the phone has booted into the stock rom, go into Settings; Backup & Reset; Factory Reset
Reboot phone, and the SD card should now be formatted correctly.
(Then reinstall your favorite Custom firmware! )

[Resolved] Huawei P8 Lite - Flashing shrinked the /data partition

Some info:
Code:
Phone: Huawei P8 Lite (ALE-L21) - 1 SIM
So, i've been rooting my device and got it working after probably 12 hours of downloading Firmwares that were corrupted and had slow download speed and flashing up to 12 updates.
I got it working, still not rooted but i can live with that. TWRP is enough.
The problem is, I've downloaded some apps, and some updates were applied from Google Play.
What I've encountered is that the memory is just 2G big!
That's so strange, because I've already had a bigger storage size before flashing.
I'll show you what's the problem:
As i've found out, mmcblk0 is the internal NAND memory.
So, we fetch the partition table which is stored in mmcblk0
Code:
/data # fdisk -l /dev/block/mmcblk0
Found valid GPT with protective MBR; using GPT
Disk /dev/block/mmcblk0: 30785536 sectors, 2744M
Logical sector size: 512
Disk identifier (GUID): f9f21fff-a8d4-5f0e-9746-594869aec34e
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 30785535
Number Start (sector) End (sector) Size Code Name
...
40 8118272 30785535 [U][COLOR="Red"]10.8G[/COLOR][/U] 0700 userdata
Ok, so now we have this information,
Partition is 10.8G big
The partition name in the /dev/block is mmcblk0p40 (as mmcblk0 is the main internal disk and "/data" partition is the 40th partition)
Ok, It's least 10G big, so, what's the problem?
We see the partition is 10.8G big. BUT...
If we use "df" we can see the real deal
Code:
/data # df -h
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p10
11.7M 7.3M 4.1M 64% /mnvm1:0
tmpfs 917.2M 16.0K 917.2M 0% /dev
tmpfs 917.2M 16.0K 917.2M 0% /tmp
/dev/block/mmcblk0p40
[U][COLOR="Red"]2.4G[/COLOR][/U] 2.4G 50.6M 98% /data
My mom's phone, that is the same phone as mine.
i(dot)imgur(dot)com(slash)dZcD1ME(dot)png
Mine instead
i(dot)imgur(dot)com(slash)Z9aybBu(dot)png
Anyone knows what's going on?
Do i need to wipe partition?
Do i need to resize fs?
Thanks beforehand

Solution:
If you have TWRP:
Wipe -> Advanced Wipe -> Select "Data" and press "Repair or Change File System" -> Resize -> Swipe to Resize
If you dont have TWRP:
Use resize2fs command