A reference to what size an image background should be set to for various screen sizes.
A background image I was using was unedited at 1600x2133 (364kb) and was not displaying on smaller devices. Configuring drawables for each layout seemed to be the only solution.
- res/drawable-ldpi 240x320
- res/drawable-mdpi 320x480
- res/drawable-hdpi 480x800
- res/drawable-xhdpi 640x960
- res/drawable-xxhdpi 960x1440
- res/drawable-xxxhdpi // for launcher only 640dpi
- res/drawable-tvdpi 1.33*mdpi // not needed as mdpi or hdpi is used
- Android Studio (Beta) 0.8.9
- Android Google Maps v2
A sequel to my article "Basic Android App using Google Maps and Current Location", this article suggests how to add Map as a sub activity. Note that this article is based on a new blank project which does not include code from the previous example but you can still build this over the previous example (as I did).
The previous article meant that the Google map was your main activity and any other activity would be a sub-activity; returning to the map activity would restart the app as a menu item, it would need to launch a new intent... I wanted to change my previous example so that the homepage of the app (the starting page) will simply display a button to the map (in case of offline mode or incompatibility with the device).
In this example, I'm going to add the map as a fragment. This is the most rudimentary example (display map, move camera and display marker) and can be run from any other activity:
A quick article on a function to allow the user to take a photo using their built-in camera or to choose an existing photo from their gallery.
I wanted both options to be available to the user and for it to replace a displayed image in an ImageView.
A quick article on how to replace the return key on a soft keyboard (software based) on a touch-device.
I have an editText where a user can enter any text value but if they typed a return character, the app would crash because it didn't understand the data. I tried replacing the new lines but just stopping the return key or trying to catch it is an obsolete method.
- Microsoft Windows 7 Pro
- Android Studio v0.8.6 beta
- Java Development Kit v1.8.0_20
The article below serves as a checklist to ensure I don't release an app that only displays maps to myself (again).
This took me a while to figure out so hopefully this will help others.
The gist is that I was using the Test SHA1 when adding allowed Android Keys to the Google APIs console (there's so many) when I should be using the App SHA1 (I have now added both to the console).