I am thinking of making a final year project as the title mentions it should be an emulator for windows phone that runs android project. i have done some research and found nothing helpful
the following discussions also shows that it is not possible
http://forum.xda-developers.com/showthread.php?t=1841481
but as we have an emulator for windows why is it not possible to have one for windows phone..
just because windows phone is locked down???
and if it is possible then what kind of programming i am looking forward to? because i know there will be alot of system level programming in this project (IF IT IS POSSIBLE)
You would probably have to look into some way of rewriting the Dalvik VM to run on Windows Phone https://code.google.com/p/dalvik/
It is not impossible but it would take a serious amount of work. BlackBerry spent a lot of time working on their own version for PlayBook.
Related
I am aware of Genymotion openGL error stack overflow question.
I am attempting to run Genymotion on a Windows 10 system, but the graphics adapter is Intel G45/G43 Express Chipset WDDM1.1 and the driver supplied does not support OpenGL and Intel appear to have no interest in delivering a driver that does for Windows 10. I understand that officially this combination is not supported.
But here's the thing: I can start a Genymotion VM fine from Virtual Box, and it appears to work (almost) perfectly, as far as I can tell.
Certainly I don't see any problem with the graphics.
This must be using some (probably Virtual Box provided) software implementation of OpenGL.
However, when I try to start the same phone VM from the Genymotion console, or from the Genymotion button inside Android Studio, I get the error dialog-box in the linked question above.
My question is: Why is Genymotion insisting that there is OpenGL support from the real physical display driver? And of course, if its for a quality reason only (ie: sub-optimal user experience otherwise) is there any way to disable this check?
The reason this matters is that Android Studio does not list the Virtual Box started phone VM as somewhere an application can be run upon. I suspect that when Genymotion runs a phone VM, they set up something that the Android Studio integration needs, that simply running from Virtual Box doesn't provide.
In addition, I can't circumvent the Android Studio integration by deploying to a phone VM using the gmtool device install file.apk command bundled with Genymotion because this is a paid license feature. As you can imagine I am somewhat reluctant to purchase such a license when I know I am running in an unsupported configuration.
Purchasing new hardware also isn't an option for me in the short term.
EDIT: The justification for this question has since evaporated. Although I can't deploy using Android Studio or gmtool.exe, I have managed to deploy by using the phone web browser to fetch the .apk file. The gotcha here is that the web server must supply a Content-Length header or the download will fail. So I now have a workable solution.
{{{ Andy
I'm part of the Genymotion team. That's an interesting question. The answer is: yes, we ask for OpenGL drivers for performance reasons. Without this, the whole Android rendering would be handle by the CPU (as soft rendering) which is not fast enough to allow a real usage of the devices, with a seamless user experience, particularly since 4.3. If you run a 4.2.2 image from VirtualBox, you'll see the UI inside the window but the rendering will be very laggy.
As you maybe already noticed, running the Genymotion devices from VirtualBox works only for images up to 4.2.2 (released 3 years ago). The other image will show only a console window. And to be honest, you should more consider it as a side effect than a real feature. This behaviour could disappear on a future release for any reason. And there is no way to disable this check.
As you mentioned, this configuration is really weird and exceptional. As far as I know, we don't plan to support these kind of configuration and I don't see any real viable solution to make it work properly.
Also, to explain the problem you encountered with Android Studio. When a Genymotion device start, it gets a local IP. This IP can be used to connect it to adb. Then it is possible to interact with the device like with any other Android device. This is the tools used by your IDE (and (m)any other tools communicating with Android devices.
Usually, the Genymotion app does this for you, by connecting the newly started device to adb. But you can do it yourself by running adb connect <DEVICE_IP>:5555. Just be careful because this connection could not be permanent and you should have to run this command regularly in some situations.
I hope this answer will help.
Cheers.
I am currently a QA intern at an app publisher and I use the AVD to test apps on various Android platforms and hardware builds. I touch nothing else within the Android SDK, just launch the android exec through the terminal and go from there.
I installed and started using AVDs with no issue about a month ago, installed the Intel HAXM with no issue, etc. It randomly stopped working for me about two weeks ago and I've been struggling with it since then. I've deleted everything from the Android SDK and reinstalled several times, tried using adb to no avail, nothing. I haven't been using Eclipse to get to the AVD Manager, but even when I do it makes no difference.
I've run into a dead end after trying every potential solution I could find on the Internet. Help me before I go insane.
Also using a Retina MacBook Pro, not that I think that'd make a difference, but just incase.
I am going to put this up as an answer just because I really found it to be the best solution to all of my native AVD issues (my default AVD emulators would creep even on my faster machines). I downloaded genymotion and must say that I am a million times happier with the emulation. It is faster, smoother, has more options, it just makes the native AVD look even worse than it already does on its own. Even if genymotion isn't for you, I highly recommend looking into third party emulators. It will make QA, development, etc. with Android that much easier. Assuming ARM isn't required (don't think it does ARM emulation)
So i'm having awful trouble trying to get the Emulators in the Android SDK to start up. I can create the AVDs just fine, and then when hitting the 'start' button from the SDK Manager, bring up the small loading console window, indicating that the emulator is launching. However, after that, nothing happens!!
I have read many threads and posts with people having the same problem, maybe to do with the settings requiring too much memory, with some people waiting 30 minutes for the emulator to load!!
When trying to run the AVD emulator through terminal, I simply get a 'Bus Error' with no further indication of what could be going wrong...could it be a memory issue?
What I did to get where I am now:
Download the Android SDK package for Mac. I'm extracting the sdk only, not eclipse. I'm on Mac 10.6.8.
Install the SDK, and download the latest version of Android in the SDK Manager, along with default tools.
create a AVD and hit start.
window pops up to boot the emulator, that process is complete and window closes.
Nothing happens.
My knowledge of the sdk tools are very limited, all I want is to be able to do some testing...
Any help greatly appreciated!
Thanks
Actually, the simplest way to get emulators running right now is probably GenyMotion. They provide an interface, and pre-configured emulator images to make it pretty simple to get running.
This is not an endorsement (I use the standard ADT myself) but a lot of people find their tools useful.
Here is my suggestion: instead of using AVD, start using espresso and virtual remote android hardware emulator from Google servers - also known as android-test-kit. You will have the possibility to run and test you App on several different devices, without the need to spend money on actually all different devices for developing and testing purposes before releasing your Apps. You find further details here:
android-test-kit
Why Espresso
The 2 videos are somewhat long, but worth watching.
Taking this approach will solve your problem, save you money, and improve your productivity.
I run into the same issue on my mac 10.6 and it only works if i do
emulator64-x86 -avd my_android
Besides, my virtual device has to configured using x86 but not ARM
maybe this link can help you.
I'm currently on a Windows 7 box with 1.83GHz processor and 1 GB RAM. I used be able to use all applications with no speed issues. I recently installed Android Plugin in Eclipse Helios and now Eclipse has slowed down badly. Running projects/creating projects/saving code changes all takes 3-4 minutes to happen. When the emulator is launched, it takes a good 10 minutes to be able to use my app. What is causing Eclipse to slow down ?? Wasting a lot of time on this. Please help.
Thanks in advance !
Your system should be running on the edge of the limit when you have Eclipse and the Emulator running. If possible work on a device or check the CPU/RAM usage while working. You should be able to see where the bottleneck is.
If you have Windows XP somewhere, I strongly recommend to switch back to XP...
Usually when your using programming envionments such as eclipse it is very taxing on your computer. The emulator taking up to ten mins to run is not shocking. I also had the same problem but if you have an android device you can use it to test your programs (its almost instant compared to the emulator.)
I want to be able to develop and immediately run android apps on my device. I've played with sl4a and a bluetooth keyboard, but the app and ide weren't designed for what I want to do with them. what are my options?
clarification: I want a mobile dev env that doesn't involve any computer (other than my android device). I'd like a simple code editor, like emacs or scite ideally, and some kind of complete interpreter or compiler for the full android api that runs on the device. I'm dreaming, clearly, but how close can I get to that today?
I've gotten Vim working really well in ConnectBot on my Milestone. I needed root privileges because of where I put the files, but you might be able to find a work around without it.
See this link:
Native Vim for Android
See also my comment after the post. I've got $HOME setup on my sdcard, and a bunch of Python plugins and colorschemes in ~/.vim/ and everything just works.
Of course this requires you to be comfortable working in Vim... I've gone back and forth with it several times in the past. It is very strange, but once you pick up a few habits and figure out its odd vocabulary it is very nice to use!
I got a pure python version of Mercurial working on Android too. It was a pain, but now I can push and pull code from my repositories and keep my /sdcard/sl4a/scripts/ folders in sync with my latest changes. I documented some of what was necessary in a bug report to py4a.
Canonical just announced that they will be bringing Ubuntu to android devices. Hopefully this will help....
http://www.engadget.com/2012/02/21/ubuntus-full-desktop-os-coming-to-multi-core-android-devices/
Like FrinkTheBrave said, you can use an ide (Eclipse is perfect, because of the Android Development Tools, but you could use any other program.
If you work on Windows, and after installing the USB driver, you only need to plug your phone to the usb and hit Run (or debug), and Eclipse will copy the apk into your Android and start running. It takes less than 5 seconds.
If you work on a Mac, you don't need to install anything, just plug in the phone and it works =D.
Well, in Linux it is a bit more complicated (though not impossible, I actually work with Linux), but you can still develop there =).
Cheers
BIG BIG EDIT
I've seen today just what you asked few time ago. Here, take it: https://play.google.com/store/apps/details?id=com.aide.ui It's obviously hard to type on a smartphone, but it could do the trick on an EEEPad transformer. Have a good day
I'm not sure about developing on Android, but you can use one of the sdks available to write your code, then copy the apk onto the device via usb and install and run it.
It takes less than a minute from saving the source code to running on the target hardware.
I use the sdk at developer.android.com and eclipse on windows xp, and use AndroZip on my phone to install the sdk. simples ;-)
I've not looked into using usb debugging, but that could be even better.