Maximum Heap Available to Dalvik in Different Android Devices

Although physical memory of Android devices are reached to 3GB nowadays, only a limited portion of this memory is available to an application. Amount of this memory may change with different version of the Android even for the same device model.

You can access row data from here


Device Model Heap Available To Dalvik Virtual Machine
HUAWEI P6-U06 268
HTC One 201
LG Nexus 4 201
Sony C6603 201
Sony C6903 201
Samsung GT-I9100 134 67 50
Samsung GT-I9500 134 100
Samsung GT-I9505 134
Samsung GT-N7000 134 67
LGE LG-F240K 134
Samsung SM-N9005 134
LGE LG-F200K 134
Samsung SM-N900 134
Samsung GT-I9100G 134 67 50
GENERAL_MOBILE Discovery 134
Samsung SCH-I545 134
Samsung SM-N9000Q 134
HUAWEI Y300-0100 134
Samsung SM-N900V 134
Samsung GT-I9295 134
Samsung SHW-M250K 134 50
Micromax A116 134 100
LGE LG-F240L 134
LGE LG-D802 134
Samsung SM-G900F 134
HUAWEI G525-U00 134
LGE LG-LS980 134
Prestigio PAP5044DUO 134
Samsung SM-N900S 134
Samsung SAMSUNG-SM-N900A 134
LGE LG-F180L 100
Samsung GT-I8190 100 67
Samsung SAMSUNG-SGH-I747 100 67
Samsung SGH-T999 100 67
Samsung SCH-I535 100 67
Samsung SGH-T999L 100 67
Samsung SPH-L710 100
ZTE N986 100
Alps S5E 100
JSR Andromax AD682J 100
Samsung SM-G7102 100
HTC Desire 601 100
Symphony W82 100
TCT Orange_infinity_996 100
LGE LG-LG870 100
Samsung GT-I9300 67
Samsung GT-N7100 67
Samsung GT-S7562 67
Samsung GT-I9070 67
Samsung GT-S5830i 67
Samsung GT-N8000 67
Samsung SGH-I727 67
Samsung GT-I9195 67
Samsung GT-N5100 67
Samsung GT-I9200 67
Samsung GT-I8190N 67
Samsung GT-N7105 67
Samsung GT-S7560 67
Samsung GT-I9152 67
Samsung GT-I9001 67
Samsung GT-I9100T 67 50
Samsung SM-T310 67
Samsung GT-I8160 67
Samsung GT-I9305 67
Samsung GT-I8530 67
Samsung GT-N8005 67
HUAWEI U8815 67
Sony Ericsson LT28h 67
Samsung SHV-E210L 67
Samsung GT-I8150 67
Samsung SGH-T989 67
Samsung SC-06D 67
Samsung GT-I8190L 67
Alps Symphony Xplorer W71 67
Samsung GT-N5105 67
LGE LG-E455 67
Samsung SC-02B 67
Sony C1905 67
Motorola DROID RAZR 67
Samsung GT-S5830i 67
Samsung GT-S5360 67
Lge LG-MS770 67
Samsung GT-I9082 58
Samsung GT-I9105 58
Samsung GT-I9105P 58
Samsung GT-I8262 50
Samsung GT-I8552 50
Samsung GT-S7582 50
Samsung GT-S7272 50
Samsung SGH-T599N 50
Karbonn Titanium S5 50
Samsung GT-S7580 50
Samsung GT-S6810 50
LGE LG-P705 50
Sony Ericsson LT18i 50 33
Samsung GT-S5282 50
Alps Celkon A900 41
Sony Ericsson SK17i 33
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)


This error occurs when you try to reinstall an android application that is signed with a different key than already installed application. This may occur if you are a developer and installed the signed version of the application to your device (from Google Play Store) and you want to install a debug version of the same application for development purposes. To prevent this you may sign your development/debug versions with the same key that you use for publishing your application to Google Play Store. To do this you have to change your debug certificate with your real certificate. Debug certificate used is stored in the .android/debug.keystore file in your home directory. You have two options:

    Export your release key from your release keystore and import it to debug.keystore Copy your release keystore over your debug.keystore and change store and key passwords to “android

I will describe steps for second option.

    Copy your real keystore (release keystore) over ./android/debug.keystore file Change keystore password to android using keytool:

             keytool –storepasswd –new android –keystore debug.keystore

    Use keytool to list keyaliases:

             keytool –list –keystore debug.keystore

    Above command will list key aliases and their corresponding certificate fingerprints. Find your key alias you have used to sign your application for Google Play Store

    Now change password of the key you have used to sign your application for Google Play Store to android:

             keytool –keypasswd –alias your_key_alias –new android –keystore debug.keystore

    Now rename your key alias (your_key_alias on above command) to androiddebugkey:

             keytool –changealias –alias your_key_alias –keystore debug.keystore

   Above command will ask you destination alias name, enter androiddebugkey. It will also ask your store password like all above commands.

After that your debug versions can be installed over the version downloaded from Google Play Store.


VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

My First Published Android Application:Kids Photo Album

Kids Album is a photo album application.

Main focus of the application is taking periodic photos of your kids and displaying them in a timeline view.

Main Features:

Create your kids profiles
Customizable reminder to remind you at which period you would like to take photos
Daily,weekly,yearly photos
Display photos in timeline
Add old photos to timeline from your phone’s gallery or other applications
Merge selected photos from timeline
Share merged photos on facebook, twitter,instagram, e-mail …

QR Code generator

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

How to Speed Up Android Emulator for Debugging and Testing

I usually prefer to use my real phone for debugging and testing my application. But I want to see it in other device configurations, especially the user interface. Even you build the user interface with a visual editor you need to see it runtime to fully visualize everything. Android emulator is very slow because it is emulating ARM code on an x86 system. Especially it is very slow to start so you should keep it open. To start it fast you may use Snapshot feature of emulator. Enable Snapshot while creating virtual device as shown below:

You have to enable Snapshot and start the device from this snapshot while launcher the emulator.

Increasing the devices RAM size to 1024M may also help a lit bit as shown on the first image. Especially on newer images.

But these will only make your emulator start fast, it will be still slow at run time. To make it fast at run time you have to use Intel’s x86 Android image. Install it using the instructions here. After installation execute the HAXM setup from <android-sdk>\extras\intel\Hardware_Accelerated_Execution_Manager folder. While creating your emulator using AVD Manager, you should select Intel x86 Atom as CPU type. For it to be enabled you have to select API level for which you have installed an Intel x86 Android Image. Note that, it is only available for API levels starting from 15. Also select GPU emulation, but this could not be used together with Snapshot feature. So you have to disable it. You will appreciate the speed difference when compared to ARM based emulator. Of course you can not use x86 emulator if you are doing hardware dependent development.

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)

Using ActionBarSherlock with IntelliJ IDEA


“Usage” section of ActionBarSherlock only give you how to configure it with Eclipse. It is a little bit different for IntelliJ IDEA.

  • Download ActionBarSherlock zip file and extract it next to your application module which will make use of ActionBarSherlock.
  • Select File->Import Module from IntelliJ IDEASelect library folder under ActionBarSherlock folder and import it as a new module. It will be imported as an Android library module.

  • Open module settings of ActionBarSherlock library module and export android-support-v4.jar dependency
  • Open module settings of your application which will make use of ActionBarSherlock and add a new Module Dependency

  • Select ActionBarSherlock from the list of modules


PS:Some tutorials on the internet directs you to add android-support-v4.jar to your application’s libs folder and add as a library dependency. Since ActionBarSherlock already includes it you do not have to do it, just export it from ActionBarSherlock. If you also add android-support-v4.jar as a library to your own module you may get UNXPECTED TOP LEVEL EXCEPTION.

VN:F [1.9.22_1171]
Rating: 10.0/10 (2 votes cast)

TTNET Muzik Android Uygulaması

TTNET’in muzik uygulaması Motorola Xoom’dan başka android tablet’de çalışmıyor. Aslında teknik olarak bir sıkıntı yok ama bu TTNET’in bilinçli olarak uygulamaya koyduğu bir kısıtlama.  Bendeki Asus Transformer tablet üzerinde bu uygulamayı çalıştırmak için şu şekilde bir yol izlemiştim:

APK dosyasını diassembly edip DeviceRestriction dosyasındaki

if-eq v0, v1, :cond_0

if-ne v0, v1, :cond_0

ile değiştirip, tekrar assembly ve sign ettmiştim. Diassembly işlemi için Easy Apk Disassembler uygulamasını kullanabilirsiniz. Bunu paylaşıp paylaşmamakta kararsızdım ama sonunda paylaşmaya karar verdim. TTNET Müzik üyesi olurken size istediğiniz her yerden dinleyebileceğinizi söylüyorlar ama daha sonra bilinçli olarak Motorola Xoom’un dışındaki android tabletlerde uygulamanın çalışmasını engelliyorlar. Bu güzel bir davranış değil.

VN:F [1.9.22_1171]
Rating: 10.0/10 (5 votes cast)

PDF vs EPUB on Android

Most of the ebooks I have purchased are available in several formats including epub and pdf. Due to my Sony ebook reader’s epub support I was biased toward epubs although I have already purchased ezPDF Reader application for my android devices. Recently I have started to read some books that are only available in PDF. For epubs on android devices I am using Aldiko application. But it has 2 drawbacks. Firstly it does not support annotations and second it is has very poor page turn performance if page contains source code. I have tried some other popular epub reader applications like Moon+ Reader. But I am not statisfied with them either. For example Moon+ Reader completely destroys formatting of source codes in epub. ezPDF reader is very fast and allows annotations on PDF files. It has also other advantages like text to speech but I do not use them. Only disadantage of PDF format is the margins around the page. But ezPDF Reader has fit to text feature to automatically eliminate these white spaces. So I think I am re-downloading my ebooks in PDF format. Sorry epub, you are a standard format but you need more time.

VN:F [1.9.22_1171]
Rating: 1.0/10 (1 vote cast)