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 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?
We have many phones, but we don't--and probably never will--have all of them.
It's frustrating that some phones cannot see our apps in the market, and we'd like to know which phones those are.
We'd like to have a simple way to have our app tested on each phone, but at this point there's no easy way to do that.
My question is: what would we as developers be willing to do to get these needs met? Is there enough demand for someone to buy all possible Android devices and charge a nominal fee for these services?
We would pay a small fee to have out app accessed and downloaded on all phones--this would give us a report of which phones could access our app. We would pay a fee to have a step-by-step test ran on each possible device so we could know it worked on that device, at least minimally.
I'm trying to make my application (compiled against 2.1) compatible with the 1.5 platform. I've handled all of the res/ folder issues, and have been able to run the app on all platforms without problems. I can run it fine on all emulators, and all devices/OS systems running 1.6 or higher. But on the only 1.5 device I have (HTC Hero), I get intermittent problems.
The only 1.5 device I have is an HTC Hero phone I got free at the Sprint developer conference a few months ago. When I test the app on that device, I have occasionally encountered a bug I've not seen anywhere, and can't find any information about.
I can install the application via the adb install command (although I get two messages about unknown commands), but after installing the app, the icon can disappear from the home screen, replaced either with a different icon or no icon.
When the app is launched in this state, rather than seeing my application name in the title bar, it reads "60.0dip". I don't use this value anywhere in my application.
I have never observed this problem on any other phone I've tested on (G1, myTouch, two Motorola Droids, Nexus One), but as I said I've only got one device running 1.5.
I'd love to get some ideas on best practices for testing our Android software, especially for AT&T devices. We're using a Samsung Captivate, on AT&T. As you know, AT&T disables sideloading (no Unknowns Sources option in Settings->Applications). We need to have our QA team load our apk file onto these devices as part of our testing and validation process. We're willing to install the SDK if needed, and upload the apk file via USB. We are not willing to root the phone.
I am making an android game, but i do not have the money to buy a developer phone. The game is not finished but i should it is testable.. and if i dont test it know i may have a big problem later... it is playable though. Is there somebody who has a real device and wants to test the game for me, just starting it up and playing it a little bit is good enough. It's a 2d airplane shoot gane, much like the old raptor game. If someone is interested please reply, i will sent you the (singed) APK and with some things i want to test (using both the buttons as well as touch screen for gameplay).
I need test my Android app on a Motorola Cliq but don't have one. Is there a testing service that will let me make a debug connection to that device so I can run some tests and find out where the code is failing. Video connections won't tell me that.
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 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.
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 am executing Monkey testing on a Android device. The command i am using is "adb shell monkey -p com.android.calculator2 -v 50000000 > monkey-calculator.txt" When we execute this command i suppose it should send 50000000 events to the device. In my case after sending event #150900 it stopped and i see a message: ":Dropped: keys=0 pointers=0 trackballs=0 flips=0" What does this message tell me?
I've been exploring the Android test package and I'm very confused on how to implement functional testing for endpoint-to-endpoint.
Consider the example below, I have 4 activities: 1. A Contact List Activity 2. A View Contact Activity 3. An Add/Edit Contact Activity 4. A Sync Contact List activity
I want to automate a few tests that will go through multiple test cases simulating a user experience: From launching the application, to selecting 'Add contact;' opening the add contact activity, entering data, saving it, going back to the list activity, and verifying the new contact was saved properly.
As I understand it, ActivityInstrumentationTestCase<T extends Activity> and ActivityUnitTestCase<T extends Activity>, are only useful for testing single activity functionality.
But what if I need to switch between 2 or more activities inside a single functional test case?
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 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?
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.