Can any one help with how to test sensor events like shake on Android Emulator.
I have found some posts pointing to openintents but can anyone explain how to use it in android 2.0 avd
http://code.google.com/p/openintents/wiki/SensorSimulator
This has some solution but while installing OpenIntents.apk on emulator gives missing library error.
I succeded the steps till the line:
If you don't have it already, install
the latest version of OpenIntents.apk
on your mobile phone.
I am stuck on this line:
I found deprecated version (not latest) of OpenIntents.apk , but while installing gives missing library error.
Any help ?
See How can I unit test an Android Activity that acts on Accelerometer? for a better solution.
Related
OK, please take it easy on me, I am new to the whole Xamarin community. I have built a simple calculator app using MVVMCross. When I run the app in an emulator everything works great. It still needs some UI attention, but functionally it all works. When I go to archive it and make an install on my phone, it installs just fine. The issue is when I go to run it. As soon as it opens I get an error message. "Calculator.UI.Droid has stopped" Open app again. I have gone through everything I can find online to do this and nothing is working.
Here is my setup:
Visual Studio 2017 Community with latest updates
Windows 10 with latest updates
Latest Java SDK
Project Properties:
Compile using Android Version 7.1 (Nougat)
Minimum Android Version 5.0
Target Android Version 7.1
Use Fast Deployment - false
Generate one package (.apk) per selected ABI - unchecked
Enable ProGuard - checked
Linking - SDK and User Assemblies
Android Phone:
Google Pixel 2 with latest updates.
Any help would be appreciative. Just let me know if you need more information. Thanks in advance
I myself are also using Xamarin, and quite often I get this problem, most times it is related to the code, so please make sure that's the case.
comment out your calculator stuff, and try running the basic app on your physical device. if that works try to find the problem, idk if you can use breakpoints because your problems happens on boot.
Recently i made an app for android through android studio, a very simple app.
But when i started the emulator to test the app i received an unusual error.
This is what the error looks like in a general form :-
WARNING:./android/base/files/IniFile.cpp:155:Failed to process .ini file C:\Users\xxxxxxx.android\avd\Nexus_5_API_23.ini for reading.
My question is,
1) What is the meaning of this error ?
2) And how do i solve this error ?
Have you recently updated the SDK tools. It sounds like it might be some compatibility issue with the tools and the emulator. Try going into the AVD manager and see if there is an update, and/or delete the emulator and re-create and see if that solves the issue.
So I have just started my first app in which I have a button and when user clicks on it then it just print the message.
But when I build the app and when I run that app on android studio's console then after opening it crashes and then it stops working.
Meanwhile I have searched for the error and they suggested me to see logcat table or the text file in which I can easily see the errors but after it I am stuck because I have no idea that how can I solve such problem.
Please help me with it.
Not sure how capable you are with android and you haven't given us much info to work with.
could you post a brief description of the logcat from launching the apk to the apk actually crashing?
the logcat is gonna be the best option to diagnose it.
Are you using the android sdk and emulator?
Have you updated the resources and api's?
If you go into the resource list there should a online repo with a whole lot more SDK bits you might find help.
What api's and android version is your apk built from and is your emulator emulating the same android build?
Could be the apks GUI resolution or script related, have you checked through it all?
Microsoft visual studios has a very good debug system and trouble shoot but I'm not sure if android is compatible as I've only used wp8 on it. Worth finding out though.
This is my first time learning IBM Worklight, so please bear with me. I was following this tutorial, however i stucked in page 14, where the tutorial tell me to "run as android project" so the project will be run on android simulator.
This is the error i got :
Could not find HelloWorklightHelloWorklightAndroid.apk!
What should i do? I also have watched this video, and everything works fine in that video (no error like mine)
Thanks for your time, any help is appreciated :D
The answer is because a BUG in ADT 22. I need to upgrade the ADT to latest version and install Android Build Tools.
The way to solve this bug (and get things working )is in my another question (which share the same problem, because i use a same android sdk) :
Eclipse Juno/Android broken, the debug is wrong and gen folder not created (R error)
EDIT
After that, you probably will get CLASSNOTFOUNDEXCEPTION because (again) ADT 22, so you need to do (a little) more things in this IBM link
Clean the project and build it again it works.
I recently got introduced to Android via a school course. Did some very simple examples earlier, and decided to installed all the required peripherals at my home computer too. I was on my way to develope all kind of cool stuff, until i noticed that something is wrong with my Android SDK or the emulator itself - it won't run any of the programs i try to.
I've got Eclipse & All the required add-ons / plugins installed. I get no error messages at any stage ( in eclipse or in the emulator itself ). Whenever i press run at Eclipse, the emulator takes it's time and starts up, but doesn't start the program, and doesn't actually show even the slightest hint of it. Looks just like if i had tried to start only the emulator. I've tried to create several different AVD's, and tried to use different versions of Android on them. No luck.
Im using windows 7 x64, and after a couple of rounds with Google, i found a few other guys who are having the same problem with the same OS.
Any help is greatly appreciated, as im running out of options here.
You need 32 bit eclipse and 32 bit JVM. There should be an error in the "console" window in eclipse if you hit run.
Click on the Menu button of the emulator to unlock it. You may then need to rerun the app.