Android Install Location Auto Not Working - android

I've set installocation="auto" in the manifest and on most devices this works.
Doesn't Work (No option to move to SD Card):
Razr Max HD (Android 4.0)
Samsung GS3 (4.0 and 4.1)
Samsung Note 2 (4.0)
Droid 4 (Android 4.0). This only said it would move to internal space however error'ed out saying there was no space (wrong).
Works:
Rooted, Incredible (4.1)
Samsung Note 1 (2.3.6)
Any ideas? It seems like +4.0 doesn't want to recognize the tag.

Some phones (such as the Razr Max HD and Galaxy S3) simply do not support moving apps to the SD card. Manufacturers unfortunately have the ability to remove this feature from their Android releases, and some use that power.

Related

How to run an emulator using Galaxy S4 configuration?

I have created an galaxy s4 emulator using this post how to open galaxy S4 emulator
but my problem is when I tried to run this emulator it takes very long time and at last it said time is out. My ram is 6GM. And I created emulator by providing 800MB ram. And my laptop screen resolution is HD.
How to resolve my problem immediately because I have to test my app in galaxy s4.
I got it working with the settings the other link holds (How to test android app in Galaxy S4 configuration using emulator?) and "Target Google APIs (Google Inc.) - API Level 17" and also I let the Emulator help by my GPU "Emulator Options: Use Host GPU".
Hope you folks get it working to :)
Samsung has not released Add-on for galaxy s4.
But we have an alternatives for the Same Configurations.
Actual:Samsung S4 (1080 x 1920 pixels, 5.0 inches (~441 ppi pixel density))
Alternative:Sony Xperia Z (1080 x 1920 pixels, 5.0 inches (~441 ppi pixel density))
Both are using Drawable-xxhdpi resource folder.
To configure Sony Xperia Z:
http://developer.sonymobile.com/knowledge-base/sdks/sony-add-on-sdk/install-the-sony-add-on-sdk/
Testing on Sony Xperia Z emulator,will effect the same result in Samsung galaxy s4.
Emulators are slow. No matter what configuration you have. So testing in emulator doesn't mean it'll give you same behaviour in the real device.
Unless samsung decided to do so, it won't be available with Android SDK as predefined config. You may need to manually set the configurations (which is what you have done). Even then the OS gonna run in S4 is customised by Samsung yet again as I said earlier you won't get it with your SDK package.

Android reference devices for responsive webdesign

Which devices (smartphone and tablet) do you recommend to buy as reference?
And what version of Android do you prefer?
Main goal: testing responsive websites in our small web studio.
Smartphones:
Samsung Galaxy — S2, S3, S4 (but S4 and S3 seem to be too expensive).
Google Nexus 4.
4.0 — 4.5 branded devices in middle cost segment.
bi-brands or Chinese devices (low cost, Android 4.1+).
Tablets (I think, only 9.7/10.1 inches not 7 inches):
Samsung (dunno which).
Chinese devices.
We have limited resources, so…
I would go for Google Reference Devices, as they always go through all Android versions, and they have always the latest version available. Right now they are:
Nexus 7 (2012 and 2013 versions). 2012 version is the most sold Android Tablet. also works as a reference Portrait Tablet.
Nexus 4
Nexus 10. Reference Landscape Tablet.
Nexus One or Nexus S for a reference Android Gingerbread device.
Then, if you have the budget, I would go for typical best sellers in all ranges:
Galaxy S2, S3 and S4
Galaxy Y, Ace, HTC Desire X
Samsung Galaxy Tab 7, 8.9 and 10.

Where can I get a emulator image or binary info of NexusS?

I want to test some apps on Nexus S devices,
can I access the devices remote or get some emulator image for it?
for the GALAXY Tab, I could get it at http://innovator.samsungmobile.com/galaxyTab.do , but seems neither Samsung nor Google provides the actual info on Nexus S
The Nexus S is pure Android. You shouldn't need a special emulator for it, just use the standard emulator with SDK set to 2.3. You can get all the details you need from the tech specs.
Depending on what your app cares about, you probably just need to set the screen size appropriately: 4.0" WVGA (480x800)
You can always create your own AVD just like you did for the Galaxy Tab. Galaxy Tab had a special AVD because of its huge size.
These are the nexus S specs. The Android version can be controlled by setting the minimum s/w version and api level.
In eclipse use this to create a new Virtual Device that has the same specs of Nexus S:
Window > AVD Manager

Can I develop for Android Tablets without an actual tablet device?

I bought the Augen Gentouch78 to start dabbing in development for Android tablets, but this device is gravely excruciating to use (and I'm returning it). Is there a way to configure the emulator to tablet specs (namely Samsung Galaxy Tab)??
You could create an AVD with similar hardware and Android 2.2. The main difference is the resolution (which is 600x1024), so you can try configuring your AVD this way:
Just keep in mind the AVD limitations; for instance, they don't support multitouch.
Install the GALAXY Tab addon by Samsung, it adds a API-8 Galaxy Tab target to the options list in the AVD creation screen.
The Honeycomb tablet require a API level 11 or 12 on WXGA skin.

Creating Emulators for the current Android phones

As I do not have the money to buy all the Android phones, is there a resource somewhere or can somebody suggest the settings that would best emulate the Nexus, Motrola Droid and HTC Magic etc. Some users are reporting problems with my app and I am thinking it may be due to the screen sizes.
thanks
These are the settings I use:
Nexus One - Target: Android 2.1 - Skin: WVGA800
Droid - Target: Android 2.0 - Skin: WVGA854
Hero - Target: Android 1.6 - Skin: HVGA
You're not going to get an exact match for the physical devices in the Emulator, but the screen sizes are correct.
Also, due to firmware updates some of these phones can have different firmware levels on. For example, a Droid could be on 2.0 or 2.0.1. The levels above are based on the lowest level each phone could be running.
This earlier question is relevant, but does not directly list configurations you can use.

Categories

Resources