Android :: Any Way To Emulate Particular Device Compatibility?
Jun 22, 2010
I program and test using the Droid Incredible. The other day my friend downloaded my alpha version, which works flawlessly on the Incredible, but crashed on his Moto Droid. I just updated my app to use 2.1 api's instead of 1.6; maybe this will make a difference? I upped my min version requirements to 7. My question is how can you make sure your app works on all phones and not just the phone your are building and testing on? Is there a way to emulate a particular device?
I'm working on a project that includes a test system for OEM devices. The supporting infrastructure is complete, however I'm having difficulties getting ROMs to run on the emulator. Of course the AVDs generated by the SDK work fine, but my next step is to run a binary intended for an OEM device. I understand that the emulator would require different drivers than a physical device, so I can't simply drop the same binary onto it and expect it to run.
Tweaking the AVDs generated by the SDK is about the limit of my knowledge. I've looked into pulling the system.img and other partitions from the ROM with ones from the emulator, but that doesn't work since the emulated hardware doesn't match what the drivers expect. I assume some modifications to qemu and some reverse engineering of the OEM ROM might be required to obtain my goal.
Assuming I have access to the binaries (but not the source) used by an OEM to construct their ROMs, what would be involved to obtain an emulator that matches the physical device, so I can run the compiled ROM on the emulator?
I want emulate my current android system of my phone.I want have full duplicate system of my current phone (i mean filesprogramms etc) at PC with possible to use it (things like 2-step auth of google, and others).I think the way to do it is restore image of system that can do ClockWorkMod. But i dosnt know how use it on emulator on my Win7.
I made my simple, custom rows and listviews. Right now, only clicking on the text of the row is valid selection area. I want the entire row, even the no-text area to be selectable. Where do I modify? Am I looking for focusing or selecting?...................
My home security system allows me to view the cameras from a browser. But, it only works from an internet explorer browser. (Even on my pc, I have to use IE for this, it won't work with fire fox or chrome). None of the ip camera apps available so far work with my q-see camera system. Is there any way to "emulate" internet explorer on the android?. I don't anticipate microsoft will be making an android-version anytime soon.
How can I emulate an onUpgrade call for my SQLiteOpenHelper class? I have tried changing the version number in my SQLiteOpenHelper class and versionCode in manifest but onUpgrade is not called. Any idea? I need to check my onUpgrade code before upload it to the market, I don't want my app's users get a buggy upgrade.
I am having few android rom backup's from my old Xperia Arc S, Wilfire, Galaxy S. All were rooted and saved their nandroid backup.The need of hour is to retrieve some data out of the Roms. But I am not having any device at the moment.So the thing I wished to do is to emulate those roms and run them on PC.
I am trying to use the android dev emulator to create a virtual phone with the same spec as the droid. I am using the WVGA 854 profile, High density (240) and scaling the emulator screen to 3.7 inch on launch. Problem is it seems to be emulating it like it has WVGA 854 resolution but with a medium or low density screen, as the icons are teeny tiny and the whole thing looks wrong. I'm sure the droid does have teeny tiny icons and apps, can anyone tell me where i am going wrong?
Is there any way to emulate an android froyo with normal kernel and everything a normal android phone has? Including a market and recovery mode. I want this mainly because I feel terrified by the thought that I might brick my phone flashing a custom rom and I am a beginner so I never tried anything complicated with it. So before I try anything over my phone I want to try this on an emulated phone.
I have a TabActivity with several tabs. Each tab corresponds to a specific view, and those views may further switch to other views. For example, one of my tabs displays RSS feed list, after user clicks one of the RSS feed, it will switch to a view displaying a list of articles, and after user clicks one of the titles, a full article view will be displayed.I'm going to add support for "back" button in my application. For instance, in a full article view, after user presses the "back" button, it should switch back to the article list view. And if user presses it the "back" button again, my application should switch back to the feed list view.My idea is to maintain a Stack<View> during navigation, and every time user presses the "back" button, the program will pop a View out of the stack, and set it as the current view. But I would like to know how to set current view in TabHost.
I looked around and although there are many related questions I didn't see one that answers my exact question:
I would like to create an app that runs in the background that provides the exact same functionality as the hard coded 'Back' button in all cases.
The reason? I (for example) have a Droid X, and it is BIG. it makes it extremely hard to use one-handed and having a swipe gesture function as a back button (like in Palm Pre for example) would greatly increase the ease of use.
as far as I'm concerned the app could just be one simple class that contains: 1) a listener for the 'back' swipe 2) a call to the physical hard button itself
Is this possible? are there built in APIs for the hard coded buttons that would allow me to call them without actually pressing them?
Again - I'm not interested in overriding the button, I'm interested in making a software call to it - or failing that, in emulating it's behavior in any and all states and other apps!
Please forgive the naivete of this post. I am a very novice programmer and really I just want to know whether this is possible before I start to devote myself to trying to build it.
I have a program that should work on Android 1.5, but when it's run on newer devices with higher resolution screens, it should support the full resolution and not emulate a lower resolution screen. As far as I can tell from the documentation, this should be simple.
I just specify
The problem is that if I tell Eclipse to compile for 1.5, it refuses to accept this. It reports an error (targetSdkVersion is an unknown tag) and refuses to compile or run. If I tell it to compile for 1.6 it works fine, of course. But if I then try to install on a 1.5 AVD, the program immediately crashes with a java.lang.VerifyError. I'm clearly missing something simple. How do I get it to compile an apk that works under 1.5, but still includes the targetSdkVersion tag?
first of all what is the resizeable attribute? It does not seem to be documented. This is working almost 90% for my game except when testing in WVGA screen resolution, all my images are scaled incorrectly, it is longer vertically than horizontally. I was expecting the screen compatibility to maintain aspect ratios as that of HVGA.
Also in my layout I have a scrollview and it is designed in such a way that in HVGA when it is not scrolled down, the items are hidden away, however now in WVGA those things are shown. If the aspect ratio of HVGA is maintained I won't have this issue. How can I make sure the aspect ratio is maintained? Also in my layout I am positioning some items using pixel positions. Should I convert these to dpi? How do I calculate what dpi they should be?
What is the recommended approach to have currently shipping 1.5-SDK compliant apps to start offering 1.6 features (such as TTL) in the Market? Can we just publish 2 versions of the same package name each compiled with a different SDK level (will the Market automatically push out only the right version of the app) or do we have to use different package name and assume that the user will find a way to understand the version of the OS he has. A public statement to the developper community would be more than welcomed here!
I've found again my DevPhone1 (aka G1) on a shelf and though that this time I should really give it a try and create an app for it. But I've really lost touch with the Android world and now I don't know where to start really. There have been many SDK releases lately for many new and better devices. Which one of these can I use with G1? What is the most recent one which can be used on that hardware (although with reduced performance) but which will enable development for rather modern Android releases as well. The firmware update received today, while recharging the phone, is 1.6. Can I go higher with some R&D build?
I can run my application on 1.5, 1.6 and 2.0 emulator and on a 1.5 device without any problems. But some of my users are reporting force close and strange menu entries (see the attachment) using 1.6 and higher version devices. This screen should look like this: http://www.taypo.com/blog/WindowsLiveWriter/TurkceKlavye0.7_6F1/settings_0.7_2.png
And the code that generates this screen is: <?xml version="1.0" encoding="utf-8"?> <PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"> <PreferenceCategory android:title="@string/general_settings"> <CheckBoxPreference android:title="@string/haptic_feedback" android:defaultValue="true"android:summary="@string/haptic_feedback_summary" android:key="vibrate"/> <CheckBoxPreference android:title="@string/sound_feedback" android:defaultValue="false" android:summary="@string/sound_feedback_summary" android:key="sound" /> <CheckBoxPreference android:title="@string/auto_caps" android:defaultValue="true" android:summary="@string/auto_caps_summary" android:key="auto_caps" /> </PreferenceCategory> <PreferenceCategory android:title="@string/layout_settings"> <ListPreference android:title="@string/keyboard_layout" android:defaultValue="TRQ" android:key="kbd_layout" android:entries="@array/layout_names" android:entryValues="@array/layout_values" /> </PreferenceCategory> </PreferenceScreen>
I've got a question as I don't have an Android 2.0 device to test on and this particular aspect seems untestable in the emulator. I've got a service that needs to be run as a foreground service. I have a notification that stops it etc, so I have no problem using startForeground instead of setForeground. However, I'd like to have 1 version of my app that works across all platforms... Is this possible? If my app is compiled with Android 1.5 and uses setForeground, then will that command actually work on an Android 2.0 device, or does it not matter which sdk was used to compile? I've tried compiling with 2.0, and surrounding the call to startForeground with a try/catch, but that throws a VerifyError when the service is started, when run on a 1.5/6 device since startForeground doesn't exist there. Can I catch and ignore the VerifyError somehow and make it work that way?
I recently enabled the app2sd functionality in my app.When i test the apk on my NexusOne (2.2) the app goes to the SD card, perfect! But when i publish the app on the market and install the same apk from the market on the same Nexus, the app2sd function is missing, I can't install it to my SD card.