Can I run an android app on pc without emulator? - java

Suppose I wanted to build a PC application but instead of that I'd make an Android app which does not access mobile only APIs. Can I run something like that on my PC? Do that by like running dalvik vm on a pc and then running the app in that?
Is there another way to run an app on PC apart from using an emulator?

No there is no direct way of doing that. The only ways of doing it are by using an emulator like for example the one included in the Android SDK (Android Studio) or Bluestacks.
EDIT: But there is no way to run android apps without an emulator unless you want to write the dalvik vm for every cpu architecture yourself!
EDIT2: Quoting #XavierFalempin from the comments section:
There was also ARC welder on chrome to run some android apps. developer.chrome.com/apps/getstarted_arc

On Linux yes: https://anbox.io/
I checked win,mac support - there is no support and there is not plans for that.
But running Ubuntu in VirtualBox is not a problem :)

In order to run android apps on pc without any emulator you will need to install any Android based OS on your PC which will remove the emulation part and just run the apps directly on the PC and as a result you will get better performance. I would suggest you to try Prime OS as the development for this OS is going pretty well and you can post your query on their forums in order to get your issues resolved asap. They have 3 separate variants for old, newer and newest chipsets which makes it compatible with most of the systems. You can download it from here : https://www.primeos.in/download

Related

Which device should i use in Genymotion to suit my computer properties?

I've tried 3 virtual devices and when I run any of them a white screen is opened without anything inside .
and i think that the VirualBox problem is the reason
here are my computer properties
I've already answered similar issue: Ubuntu Linux 32bit - not a Genymotion virtual device
Genymotion already does not support 32-bit computers, so I suppose that you're running older version or you're trying to run 64-bit version on 32-bit.
With 2GB RAM and 32-bit machine I would have forgotten about any emulator - Genymotion, Android SDK emulator and others.
Look, building small sample application in Android Studio may freeze your computer as it takes more than 1GB RAM and you want to run also an emulator which takes also more then 1GB RAM and I suppose also web browser (Chrome) and other software.
If you really need to work on this pretty weak computer, I suggest you to buy a low-end Android devices and forget about emulator.
It would be good also changing Windows operational system, which seems to me a bit heavy to lite Linux operational system like Lubuntu or Elementary OS.
Hope it will help

Sending data via bluetooth between Android phone and laptop running OS X

It seems like a relatively mundane task to make an app that can send data via bluetooth but I've been banging my head on this for the past few days so I'm looking for any ideas. I'm running OS X 10.10 and using a Nexus 5 Android device. Here's what I've tried so far:
I need a server program running on my laptop and I need a client-side android app running on my phone. However, (correct me if I'm wrong) the server program running on my computer needs to be able to access the Android Bluetooth API because I need to use the BluetoothServerSocket (based on the server-side code provided in Google's Android Bluetooth tutorial).
Since it's server-side code, I need to run it on a server so I built a Java Servlet which I ran from inside Eclipse but I didn't know how to access the Android API from inside a dynamic web application.
So I started following this approach where the Bluecove library made that possible: http://luugiathuy.com/2011/02/android-java-bluetooth/
I tried getting Bluecove to work with OS X but there are a whole host of issues involved with that. I found some workarounds and then got an error dealing with the IOBluetoothLocalDeviceReadSupportedFeatures device that Apple removed in its later OS versions (but Bluecove depended on it).
I found a fix here that installed the old IOBluetooth library and changed the DYLD_LIBRARY_PATH to point to it. Unfortunately, this had no effect (I don't know if I changed the library path properly...I followed the instructions from Solution 1 in the answer from this post).
In any event, I feel like I'm overcomplicating this task and am looking for any guidance - in terms of overall approach or a specific thing I missed. The primary issue is accessing the Android Bluetooth API inside the server program intended to run on my laptop.
I eventually ended up using WiFi to send data since there was better software support for that.
But if someone wants to pursue the Bluetooth path, one possibility is to run OS X Lion (which had the IOBluetooth library) as a VM and run the server-side Bluecove code on the VM. This would require a separate Bluetooth USB dongle to be attached because the VM can't access the bluetooth hardware of its host machine - there may be a way but by default it can't access the in-built bluetooth hardware.
Not an ideal solution but I don't know if there is much choice until Bluecove releases a version that is supported on recent OS versions.

Running Android emulator on computer with AMD processor

Is there anyway to run Android virtual devices through Eclipse while operating with AMD processor? I had Genymotion for a while and despite it worked, it was too much of a kerfuffle to dabble with it.
For AMD processor, create a new Virtual Device and while selecting the system Image select the ABI as armeabi instead of the default x86 one.
You don't need an Intel processor to run the emulator, it's just so much faster with the HAXM technology which obviously is not available to you. I recommend buying a cheap Android device for testing, as none of the emulations provided with the ADK are particularly fast.
With developer mode enabled on your Android device, you'll find the debugging and all other useful features that Eclipse provides work very well (but note that developer features are now quite hidden: http://www.theandroidsoul.com/android-4-2-developer-mode-is-a-tricky-thing-heres-how-its-done/ ).
Use Genymotion insted of default one. It is way faster than the default one. And yaa the emulator is compatible with both Intel and AMD. Genymotion just uses Virtualbox to run Android in VM.
Genymotion Home Page

Android emulator unbelievable slow in Windows 7

I have a nice PC Desktop that I run all my development applications, Visual Studio, SQL Server instance running, Eclipse, Spring Eclipse etc... everything is fairly fast.
But when I run a simple, little, empty android hello world app, it takes literally 3 or more minutes for the Android get started!!! I don't believe I am the only one experiencing that? I don't want to run in the device every single time... usually it is handy run in the emulator just like I do with XCode to IPhone simulator...
any experience with that? solution tips?
thanks
You can use android-x86 (helpful post). x86 port works faster than emulator, but I recommend use a real device to avoid emulator-specific problems.
The Android emulators, especially the older ones, are notoriously slow. This is because they not only have to run an OS in an OS, but they must also emulate an ARM processor Architecture, on a x86 or x64 processor. This makes them rather slow.
However, you do get Intel images for ICS, which are built for x86 and run faster. You could also try using the older emulators. They got progressively slower upto honeycomb. You could also try increasing the emulator RAM and get a minor speed boost.
Other than that, you could leave the emulator running once started, as then it's much faster to test your apps, since you don't need to start it up everytime.
However, I would personally recommend testing on a device, as you will never get the same quality and accuracy in debugging on an emulator.
There is an Android emulator called Bluestacks that you can use for apps as well. It is less for development and more for playing Android games on your PC, but if you don't mind testing your app in a non-standard launcher environment then it is super fast.
You can even use it for debugging and access DDMS from Eclipse as well by following these steps:
Open Bluestacks
In your 'platform-tools' folder in command prompt, type "adb connect 127.0.0.1"
Try to run your app or debug from Eclipse and you should see a new device listed for Bluestacks.
It doesn't have the same type of hardware/environment emulation that the normal emulator does, so it will not be appropriate for testing all apps, but I use it whenever I can because the normal emulator is such a headache.
So far, there is no solution for that...I have to buy a nexus to run my apps to make the development viable

Using Android libs on a desktop Java VM (like OpenJDK or OracleJDK)

I have never tried out the Android SDK and do not own an Android phone. However it seems that certain libraries are excellent, for example the text to speech lib. Is it possible to use this library with a desktop VM and did anybody here try this?
You could get the sources from android.git.kernel.org and try to rebuild them against a desktop environment, but it would be a lengthy project - you need not only the java stuff, but the underlying drivers, native libraries, customized c library, and add-on os functionality to support them.
The android SDK includes a qemu-based phone emulator in which most functionality works as on the device. This should be fine for playing with the capabilities, though is not something you would want to use to deploy them. There is also an x86 community build of android which people put on netbooks or run in virtualbox. Word is that the official android emulator may be moving to something similar since it's substantially faster to run x86 code on a customized os image in a vm than to emulate an arm processor.
There's also something of a simulator which tries to provide enough of the android o/s services to sort of run apps natively on the development machine without a vm, but the google folks have implied its a bit of a hack and not well maintained.

Categories

Resources