When I create a new Android 4.4 virtual device using AVD Manager, I can’t get more than 200 MB of internal memory.
512 MB is the size of the internal memory I want to install.
This is done on ARM and Intel Atom x86 processors.
If I upgrade to Android 3.0 (ARM) now, I can customize the format using AVD Manager. Is there a problem with Android 4.4? Did I miss something? Or a possible job?
How can I solve this problem?
Since the file system of the emulator is ext4, I was able to reduce the file userdata.img using standard Linux tools.
# Remove old image
# Reduce image
resize2fs userdata.img 512M
# Start emulator and enjoy
I could also directly adjust the size of userdata-qemu.img, but first I had to run e2fsck.
e2fsck -f userdata-qemu.img
resize2fs userdata-qemu.img 512M
In addition, the above suggestion may cause the Android emulator to hang from the startup logo. The reason for this is that resize2fs makes changes that are usually correct, but are considered broken by Android and do not allow to go to rw mode, freezing the boot process.
Examination of the start-up log shows something like this:
EXT4-fs error (device mtdblock1): ext4_mb_generate_buddy:741 : Group 2, 32366 clusters in bitmap view, 32370 in gd
The e2fsck event does not solve the problem for Android, and to work around it, I use tune2fs to change the way Android broken fs should continue to mount.
tune2fs -e sequel userdata-qemu.img
Somebody 13, this is definitely the finish bug: Android 4.4.2 – PLC level 19.
I have the same problem – when using Android 4.4.2 in the Android SDK emulator I can’t change the size of the internal memory of the device under any circumstances (even with disk.dataPartition.size=xxxM in config.ini or with command line arguments – partition size xxx).
The only way to set a custom size is to use it as a target: Android 3.0 – API level 11.
My gear: Windows 7 Ultimate SP1, 4GB RAM; Core Duo 2.28GHz; GT630
If you still have this problem in 2016, try removing the AVD Manager image and adding the emulator again.
It looked like I couldn’t adjust the size of the emulator, which I did, but it worked when I removed the image and then re-created it with 1 GB of internal memory.
Solution No 5:
I could create this virtual device, maybe change the type of device or something?
Solution No 6:
For building based on @Frohnzie’s response, resizing2fs and e2fsck are now included in the SDK tools (you may need to update the SDK tools to see them), so you don’t have to install them separately. They can be found in your AndroidSDKFolder/tools/bin64 (Windows, Linux) or in yourAndroidSDKFolder/tools/bin64 (Mac, Linux).
Solution No 7:
Assaf G’s answer is good. However, I have learned from the following links that the first user can create an emulator with 500 MB internal memory. However, there are some exceptions, but these do not relate to the internal memory.
And the other link allows the user to create an emulator with 4096MB internal memory. But he has speed problems. Please try the specifications in the first link.
Android 4.4 Emulator
emulator 2.android forever startup
Solution No 8:
I had a problem when I accidentally chose the AOSP 4.4.2 emulator in Android Studio. Google Inc. s x86 emulator (below) does not seem to have this bug.
Solution No 9:
Deleting /data/data/com.google.android.gms/files will release 200M+.
Solution No 10:
There seems to be a catch here, it doesn’t work in the old Android tools under version 22. I upgraded my android tool to 23 and it started working.
My configuration was
API level 21
CPU : Intel X86
OS : Ubuntu Linux
android studio emulator not showing app,android studio emulator black screen,intel x86 emulator accelerator,no emulators found as an output of emulator,could not start avd in android studio ubuntu,waiting for all target device to come online,android studio download,android studio online,android studio features,android studio tutorial,android studio emulator,update android studio,ru scanner ru config xml,enterprise browser installation,zebra tech docs enterprise browser,enterprise browser download,zebra enterprise browser api,zebra enterprise browser default password,emulator: emulator: error: not enough space to create userdata partition,low disk space on a android studio system directory partition