How to solve: "Failed to push selection: Out of memory" I Create an article in Stack overflow. But as I found this site, I decide to ask the same question here, because I still need your help. 

I have made the following steps:


Launch Eclipse
Go To: Window -> Open Perspective -> Other ...
Select DDMS from the opened dialog
Select "File explorer" tab.
Press "Push a file onto the device" and select library which I wish to push.


  Failed to push selection: Read-only file system

Minimize all opened windows and open Command Line
Write: cd C:\android\android-sdk-windows\platform-tools enter
Write: abd remount enter


  You will see remount successful

Maximize Eclipse and try step 5.


  Failed to push selection: Out of memory



Error appears! What to do to solve this problem ... Please help.

ADDED

1) When I write ADB SHELL MOUNT:

rootfs / rootfs ro 0 0 
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0 
none /acct cgroup rw,cpuacct 0 0 
tmpfs /mnt/asec tmpfs rw,mode=755,gid=1000 0 0 
tmpfs /mnt/obb tmpfs rw,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/mtdblock0 /system yaffs2 rw 0 0 
/dev/block/mtdblock1 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/vold/179:0 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 
/dev/block/vold/179:0 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,size=0k,mode=000 0 0


2 ) Shel Prompt starts with: #
Launch the emulator from the command line so that you can specify a /system partition size using the -partition-size &lt;MB&gt; option. For example, I use this to launch an emulator running Android 1.6 with a /system partition of 512 MB:

emulator -avd Donut -partition-size 512


...where "Donut" is whatever you named your AVD (you can check in Eclipse's AVD manager if you need to). The emulator binary should be in your tools/ directory within your SDK install, which for you appears to be C:\android\android-sdk-windows\tools, so be sure you cd into that directory first (or add it to your system's %Path%).

Eclipse may not pick up the emulator right away, or it may recognize it and then drop the connection. If either of those happens, click the view menu on the Devices tab (the little arrow next to the minimize button) and select "Reset adb" to get the connection back.

Once it shows up in your devices, do what you were trying to do earlier. Run adb remount to get the /system partition in read-write mode, then use Eclipse to push the file wherever you want. I tested with a couple of random files a minute ago and was able to push them to /system/xbin without any trouble.

For reference, here's the partition size and use of /system on my Donut emulator when I specify a 512 MB partition:

&gt; adb shell df
...
/system: 508416K total, 61332K used, 447084K available (block size 4096)
...


But here's how it looks if I launch without specifying a size:

&gt; adb shell df
...
/system: 65536K total, 61204K used, 4332K available (block size 4096)
...


Additionally, you can set command line options in your application's run configuration via Eclipse if you want to. Go into your Java perspective, then select Run-&gt;Run Configurations from the menu bar. Select your application in the left pane, and then pick the "Target" tab. At the bottom is a text box labeled "Additional Emulator Command Line Options", and you can add -partition-size &lt;MBs&gt; to that text box so that the emulator launched when you run your application will have a larger /system partition.

Note: You may have to add also -no-snapstorage or other options, to disable loading the existing snaphot, to the command line. It did not work without it for me.