Is there a way to change the default browser in an android emulator using some code running outside emulator. We want to change the android device default browser programmatic manner.
Is there a way to change the default browser in an android emulator using some code running outside emulator.
That is impossible in two ways.
First, it is impossible for an SDK application to change the default application, other than to make itself not be the default.
Second, it is impossible for an Android device to run an Android application that is not on the Android device ("some code running outside emulator").
Related
I am trying to automate the test of a qr reading app, i am able to change the image that shows as soon as a i open the camera with a virtual scene, however if i change either Toren1BD or rename the custom.png file while the emulator is running then i need to close the app an reopenit to see the changes, is there anyway to make it so that the image can be change without having to close the app?
I am using the emulator that comes with android studio and the testing script is done in Katalon
When I open default browser using Appium, instead of given url, it opens default home page. Never mind if I set the home page to blank page, or something else. It works fine when opening browser manually, but when appium opens it, it is again set to default page.
I tested 2 devices with Android 4.1 and I always get the same issue on both.
This issue does not happen with Chrome browser.
Has anyone had this problem?
If you want to work with the stock Android browser using Appium, i suggest you run your tests on an emulator instead of the real real device.
Appium is compatible with Chrome on real Android devices but you can run the tests on the Stock Android browser if you use an Emulated device.
I have tried it out and it works.
Cheers
Is it possible to change the enforce a particular orientation of screen in a gwt+mgwt application? Lets say I would want the users to always use the application in landscape mode.
It depends: yes as phonegap app and no inside the browser.
If you are running as a web application you dont get any control on the orientation. The browser handles that for you. But if youre running as an application with phonegap you can set the supported orientations inside your app (same as every native app).
With iOS this would be inside the normal configuration of your app. On Android this is inside your android manifest file.
I have written an application using Adobe Air 3.4 SDK. I have deployed it to my android v4.0.4 device. It works fine (in full screen mode as expected).
Now the application is expected to run in full screen mode automatically before the device shows the native android screen to the user.
How can I do this? Suggestions anyone?
In the AIR native classes, there is a thing called startAtLogin that you can set to true or false :
NativeApplication.nativeApplication.startAtLogin = true;
But I doubt that can be used to override the native android screen and be displayed before it.
I suppose some built-in checks have been made to be sure nothing gets booted before the screen is ready and diplayed.
Still, you can try it :-)
I am trying to write an application with Mono for Android. In an attempt to do this, I'm using the default template in monodevelop. I can successfully compile and run the application. When I run the application, it looks similar to the one shown here: http://docs.xamarin.com/android/getting_started/hello_world
There are two oddities in my version though:
The button is red
I can't seem to actually click the button. When I use my computers mouse, it acts like it won't click the button. This is not limited to the application either. If I try to click the home or search button in the emulator itself, I noticed that nothing happens either. Its like the emulator is not responding to my mouse.
As someone new to working with Android, can someone please tell me what I'm doing wrong? I'm using MAC OS X with Lion installed. I'm assuming that I have the SDK and Java SDK installed properly considering the app compiles and when I press "play" I can load the app in the emulator. I just can't figure out why I can't actually click the button. So bizarre.
Any ideas?
The title of this question is pretty misleading, since you're saying that the emulator is not very responsive even outside the Mono for Android application. The problem here is with the emulator itself. The one thing I would recommend trying with respect to Mono for Android is to try starting the application without debugging, as debugging will add extra overhead to running the app.
The Android emulator is notoriously slow, since it is fully emulating the ARM instruction set in software. That said, there are certain things you can do in order to squeeze some more speed out of it. One thing that I've seen make a big difference is to decrease the screen size of the emulator image. Setting this to a small screen size (such as QVGA) can make a big difference. You can manage these settings through Android's AVD Manager.