Related
Does anyone know of any VirtualBox Android Emulator that has Marketplace?
Thanks!
Oh, I forgot to add "that's free" and not the $50 that some cheeky bastards are trying to charge for a thing called AndroidVM!
iridium21 said:
Does anyone know of any VirtualBox Android Emulator that has Marketplace?
Thanks!
Oh, I forgot to add "that's free" and not the $50 that some cheeky bastards are trying to charge for a thing called AndroidVM!
Click to expand...
Click to collapse
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.
attn1 said:
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.
Click to expand...
Click to collapse
I'm already running Android under Virtualbox - I just wondered if there's a version for VB that has Marketplace.
attn1 said:
Android doesn't just load up and run on a PC. It's a source code project that a real developer has to spend time porting from platform to platform, unless you want to run it from a runtime built from the SDK. To do that requires an underlying OS, like Windows, Linux a MAC - something capable of running the SDK.
Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already.
Click to expand...
Click to collapse
Wow. So much complete and utter wrong in one post... I've been running Android under a virtual machine for quite a while...
There is an x86 version of Android available at androidx86.org
It will definitely run under Virtual Box or any other virtualization software package. It's Android 1.6 by the way, and you will have to perform some geek-like activities to simulate an SD-card to install appz.
Big question is whether an ARM-device version of Android would work in a normal VM emulator (not talking about Bochs and stuff).
FloatingFatMan said:
Wow. So much complete and utter wrong in one post... I've been running Android under a virtual machine for quite a while...
Click to expand...
Click to collapse
Well, since I hadn't heard of a port to x86, I was certainly wrong about that, which makes the rest of the post moot, but not wrong. In any event, I stand corrected.
sorry to add a flame of any kind but this
"Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already."
is totally wrong.
Virtual machines virtualise the hardware of your machine (bad explanation I KNOW). if you have a PowerPC you can only emulate PowerPC (Mac for those that dont know) and intel/amd chips are things like x86 then theres smaller devices like ARM. my point is that if you have a Intel/amd box you can only emulate x86 O/S. however if you have a netbook with a version of linux or windows built on arm arch then u could prob get away with the original android if you are running normal x86 then u require android that has been built from source on x86.
this made me laugh
"Since Android is built on a Linux kernel, it's not impossible"
all i can say is what??
anyway back to the point... to run android on a x86 box u need x86 android
The problem with getting the Market to work is simply that the GApps are currently only available in a compiled for ARM version. period. that's the answer you wanted to hear i guess.
@others: stop OTing please...
hvc123 said:
sorry to add a flame of any kind but this
"Since, VMware is emulating a PC, then in order to run as a real virtual machine, android needs to be pretty much ported to a PC. Since Android is built on a Linux kernel, it's not impossible, but geese - why? That said, it's bound to show up on an Intel compatible tablet at some point, if it hasn't already."
is totally wrong.
Virtual machines virtualise the hardware of your machine (bad explanation I KNOW). if you have a PowerPC you can only emulate PowerPC (Mac for those that dont know) and intel/amd chips are things like x86 then theres smaller devices like ARM. my point is that if you have a Intel/amd box you can only emulate x86 O/S. however if you have a netbook with a version of linux or windows built on arm arch then u could prob get away with the original android if you are running normal x86 then u require android that has been built from source on x86.
this made me laugh
"Since Android is built on a Linux kernel, it's not impossible"
all i can say is what??
anyway back to the point... to run android on a x86 box u need x86 android
Click to expand...
Click to collapse
VMware and Virtualbox emulate PC hardware. Since Android runs on a Linux kernel, and Linux was originally developed for an x86 PC, it follows that a port of Android could be done for a PC. Since this was not a generic discussion about virtual machines but a specific discussion about PC emulation, I don't see where the argument is.
PC = x86 and it's successors. You said I was totally wrong and then pretty much made my case. The only point I missed is that the work had already been done. To run Android in a x86 (PC) VM, you'll need an X86 (PC) compatible version of Android - right - what I said.
Right... Ok, now does anyone know the answer to the original question?
the_fish said:
The problem with getting the Market to work is simply that the GApps are currently only available in a compiled for ARM version. period. that's the answer you wanted to hear i guess.
@others: stop OTing please...
Click to expand...
Click to collapse
OP should read your thread.
arctu said:
OP should read your thread.
Click to expand...
Click to collapse
I have
Supposedly, these guys have Android with Marketplace for VirtualBox:
http://www.androidvm.com/home
So it must be able to be done - the only problem is that it's $49.95!
deleted
zgornz said:
They state they are running Ubuntu in a VM, then installed the Android emulator in Ubuntu, then the android emulator is setup to have the Marketplace. The android emulator is doing the ARM emulation.
I think using qemu User Mode emulation it might be possible to actually launch the Marketplace and apps via android-x86 without using a phone emulator. Not sure it would be that valuable, but it would allow lots more apps on a netbook running Android.
Click to expand...
Click to collapse
I imagine it would be a mess to get a touch screen working in android running on an emulator.
I read reviews on androidx86 booted (not emulated) on a few netbooks that ran great and very responsive..I also read one on a touch screen comp that worked fine..they claim all apps work-minus gapps obviously.
I plan on trying this on my Toshiba nb205 netbook today and can post a review if anyone is interested..
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
A review would sure be appreciated. More knowledge is always better.
Just a quick follow up, I tried out the Androidx86 on my netbook this weekend, both booted off the usb and installed on the hd..it runs..nothing spectacular and slightly dissappointing. You still only have a 4x4 screen and the Marketplace is entirely different, very small selection of "blah" apps..none of my favorite android apps anyways-facebook,twitter,gmail..not really any widgets either. Lastly, you need to use an external mouse..the touchpad just moves the background but gives you no pointer (could be a hardware compatability issue tho)..
On the positive side, the internet was very fast and resume time was almost instantanious..not really any major bugs, just nothing too special..
This method works with 1.6 as originally described here:
link-> forum.xda-developers.com/showthread.php?t=529170
I got it to run with the signed-dream_devphone_userdebug-img-14721.zip image from HTC for the developer phone.
link-> developer.htc.com/adp.html
I replaced the android-sdk-windows\add-ons\google_apis-4_r02\images\system.img with the one from the signed-dream_devphone_userdebug-img-14721.zip
(you should backup the original system.ini)
I then used the Android SDK GUI interface to create a Google API Level 4 machine.
I did not need to install the marketenabler.apk, as described in the original thread.
It boots up like a new Dev Phone, it behaves like there is a valid SIM and working data connection.
CTRL-F11 rotates the screen (slide out keyboard).
I have only installed a few free apps (K9 mail) but they seem to work fine.
I can't post links so copy, and paste them.
It would be trivial to create an Ubuntu virtual machine and then install the Android SDK inside of it and modify the system.img. Installing the SDK on your own machine probably takes less space and resources then running it inside another VM.
attn1 said:
Well, since I hadn't heard of a port to x86, I was certainly wrong about that, which makes the rest of the post moot, but not wrong. In any event, I stand corrected.
Click to expand...
Click to collapse
Updated, not corrected.
Yes, you were absolutely correct except for being out of date, because that process you described has already taken place as others have now pointed out.
To the person who said he was wrong, actually, no.
Android as it stands on the phone, is an ARM system compiled in ARM machine code. Android apps are hardware/platform agnostic but the operating system is not, it does have to be ported and recompiled for any different hardware system. That being said, it seems that most of that work is finished, ala androidx86.org
Cheers,
Rob
x86 Android Market
I have been reading a bit. It seems that it is possible to have Gapps installed for x86.
Froyo, people have been using Cyanogen 6 Gapps for Tegra.
Android x86 launched their Gingerbread version not long ago. It would not surprise me if Cyanogen 7 Gapps worked with it. Different devices used different versions and now there is just one version for all. It should be possible to run VM from the desktop.
NDK dependent Apps: in theory, it may be possible taking the apk using android apk tool, x86 NDK from the x86 build and rebuild it for x86 code.
I will be playing with an old EEE900 and see how this goes sooon.
Hi Guys,
I would like to create simple app with NATIVE code which run in emulator.
It is not possible to use solution in http://forum.xda-developers.com/showthread.php?t=1299134&highlight=developer+guide because it's use some ARM code.
Do you have any idea how make things work?
Thank you,
Ch.
You actually could (msotly) use that guide, but you would need to recompile the ARM portion for x86. My guess as to the best way to do this would be to use the "Platform Builder" for CE6 or CE7, instead of using the WinMo 6.5 platform as your target. WinMo only shipped on ARM devices, so far as I know, but the underlying OS, Windows CE, is very portable and the tools for it support building on a wide variety of architectures. WP7 is built on a version of CE somewhere between CE6 and CE7.
Otherwise, the stuff about using ATL, making a COM library, using ComBridge from the WP7 app, etc. all still applies.
That all said... why would you want to do this? Do you not have an actual phone to test on? Porting between ARM and x86 isn't *that* hard, but you shouldn't just assume that it'll work in all cases, so it makes a lot more sense, if you're building native code, to build and test for the same architecture you're planning to release on.
Additionally, the emulator may be missing some of the libraries that are present on the phone.
Thanks a lot. I will try it.
This is very beginning of my school project. I want only demonstrate that is possible to run some native code on WP7. Next phase of project will be on real device which I don't have right now..
Well, good luck, but I'd tend to say you're setting yourself up for a risk of failure. I don't know what it will take to use the CE Platform Builder for something like this; I have it installed but have never tried using it.
There may also be a way to compile for x86 using the WinMo build tools; I think some of the old "emulators" for WinMo were also x86 virtual machines (much like the WP7 emulator is). I never tried, though.
Risk of failure? I don't see how. The hardest part of this is finding a way to get his .exe on the emulator device and unlocking it. If he isn't using ARM ASM in his project, "porting" to x86 (or any other processor WinCE supports) should be trivial as long as a sufficiently complete SDK is available. The main issue with x86 on newer Pocket PC-like targets is that there are no Pocket PC SDKs targeting it newer than the Pocket PC 2003 one. If you want to use newer WM5 only features like GPSAPI, you'd probably need to use a CE 6.0 SDK instead.
If he doesn't want to do real time debugging, any of the Windows CE development tools or even 3rd party tools like Bloodshed DevC++, CE gcc/MinGW or FreePascal should all suffice. Windows CE is a very backward compatible OS so even an application targeting the CE 2.11 platform/SDK should still run on WP7 when you are careful to use supported APIs.
If you don't want to install Platform Builder and generate your own custom OS to base an SDK on, there are plenty of SDKs to choose from. Of course, some are worse than others. If you are using the CE 4.2 or 5.0 STANDARD_SDKs, you might become a bit frustrated when you realize they are missing many basic things like the Windows CE SIP APIs. (something that has been available for CE since 1.01 in 1997). But if you don't care about using the latest native CE kernel features and still want to use a newer IDE like VS2005/VS2008, the CE 5.0 STANDARD_SDK should be enough if you are careful. Though, I usually install things like eMbedded Visual C++ 3.0 and 4.0 along with all the Pocket PC and Handheld PC SDKs just in case I need a header or lib file that one or the other is missing.
The following MS SDKs can target x86:
-eVC3
Pocket PC 2002
Smartphone 2002
Handheld PC 2000
-eVC4
Pocket PC 2003
Smartphone 2003
STANDARDSDK_400
STANDARDSDK_401
STANDARDSDK_420
STANDARDSDK_500
-VS2005/2008
STANDARDSDK_500
Another useful x86 SDK I've found is the one for the Allegro CE/DOS Field PC:
http://www.junipersys.com/Juniper-Systems/support/Developers/Allegro-Field-PC/Allegro-CX
Here are some download links to many of the CE SDKs and compilers that were released over the years:
Here are some links to download some of the tools I've mentioned:
http://www.hpcfactor.com/developer/
http://www.microsoft.com/download/en/search.aspx?q=embedded visual tools
You will need SP4 for eMbedded Visual C++ 4.0 if you wish to use newer SDKs with it.
http://www.microsoft.com/download/en/search.aspx?q=pocket pc sdk
Ummm... maybe you missed the part where this is WP7 forum, and the OP is trying to run native code on the WP7 emulator... I can tell from your post that you're not terribly familiar with WP7 development, so here's a few salient points:
Compiling to a .exe is a waste of time. WP7 won't run foreign EXEs, at all, unless you make some pretty low-level changes that aren't possible on the emulator (see "full-unlock" custom ROMs). You have to write a managed app (which compiles to a DLL hosted inside a low-privilege EXE that's built into the system) and a COM library and use the InteropServices ComBridge API. So far we haven't even gotten P/Invoke to work.
WP7, especially Mango, uses a limited set of native APIs and the APIs have changed somewhat in the last decade or so. They aren't supposed to be available to third-party devs at all, so any backward compatibility is basically a convenient accident. Targeting Smartphone 2003 *might* work, but then, it might not. Even a number of WinMo 6.5 APIs aren't available or don't work.
Since it appears that the OP is just going for a demo project, he or she probably is a lot less interested in getting the most powerful APIs, and is probably hoping for something closer to invoking a MessageBox from native code.
All that said, however, it's true that there are WinCE SDKs which can build native x86 code. I'd tend to suggest using the CE6 or CE7 Platform Builders, since they're the most recent (WP7 is somewhere between the two), but there are other options. You probably want to follow the guide as much as possible, including things like using ATL, as it makes writing a COM library a lot easier and that's the best way we currently know for executing native code in WP7.
I've attached the Windows RT binaries for NewWolf and EcWolf, both of which are Wolfenstein 3D ports.
NewWolf features OpenGL rendering, but does not have any sound support because the port uses a proprietary (ie: no source code) sound engine. To run NewWolf use the included batch file as there is an issue with 16bit color depth (the batch file will force 32bit).
more info -> http://newwolf.sourceforge.net/
EcWolf is straight up software rendered using SDL with full sound support and is very true to the original. Simply run ecwolf.exe.
more info -> http://maniacsvault.net/ecwolf/
I have also included the original Wolf3D 'demo' game files so people should be able to play this straight away. If anyone has concerns about this, let me know and I'll remove the game data.
These are also on the SVN repo, so feel free to pull it from there if you like.
Cheers!
The original game files were shareware I think, I dont think anyone can complain about you throwing in shareware files for an old game.
Nice work yet again. I was just about to ask if you had considered doom, but it seems you've already done it
Offtopic.
SixSixSevenSeven, i see you know a lot of about Windows RT and porting apps, and i have a Little question. I need a C Compiler for my Bachelor of Science Degree in Computer Engineering, and i don't have any laptop for running a C Compiler. I'v tried searching a C Compiler for Windows RT (I'v only seen a C# Compiler) and i want to know if will be possible to run something like gcc in Windows RT, saving money buying a laptop.
Thanks
comandospi said:
SixSixSevenSeven, i see you know a lot of about Windows RT and porting apps, and i have a Little question. I need a C Compiler for my Bachelor of Science Degree in Computer Engineering, and i don't have any laptop for running a C Compiler. I'v tried searching a C Compiler for Windows RT (I'v only seen a C# Compiler) and i want to know if will be possible to run something like gcc in Windows RT, saving money buying a laptop.
Thanks
Click to expand...
Click to collapse
Not yet. MinGW might run under the x86 emulator but anything it produces will also only run under the x86 emulator, and that emulator isnt 100% reliable and it is rather slow.
You would be best off with a laptop, sorry.
Also not really something to be discussed here.
SixSixSevenSeven said:
Not yet. MinGW might run under the x86 emulator but anything it produces will also only run under the x86 emulator, and that emulator isnt 100% reliable and it is rather slow.
You would be best off with a laptop, sorry.
Also not really something to be discussed here.
Click to expand...
Click to collapse
I tried MinGW under Win86Emu but the setup doesn't work properly. I found a Little C compiler (Tiny C Compiler) and works perfectly with Win86Emu (at least some simple code), so i think that this could save me temporarily from buying a laptop.
Sorry for asking about this here, but thanks so much for the Win86Emu idea
Already exists?
There is a Wolfenstein port in the Windows app store called Wolf.
Surface-RT said:
There is a Wolfenstein port in the Windows app store called Wolf.
Click to expand...
Click to collapse
Looks like it only has the 1st level based on the comments... a Demo of sorts I guess. These ports would allow you to play the complete game, assuming you have access to the game files. I have no idea if you could use the complete game files with this Store version.
I haven't actually tried either of these ports yet. But I am curious on whether they are an improvement over the original DOS game? I've played that a bit using DOSBox on my Surface...
domboy said:
Looks like it only has the 1st level based on the comments... a Demo of sorts I guess. These ports would allow you to play the complete game, assuming you have access to the game files. I have no idea if you could use the complete game files with this Store version.
I haven't actually tried either of these ports yet. But I am curious on whether they are an improvement over the original DOS game? I've played that a bit using DOSBox on my Surface...
Click to expand...
Click to collapse
This port is running natively, otherwise it is essentially the same as the dos version. But running natively means it requires less CPU power (no x86 + DOS emulation) which might help keep the tablet cooler and prolong battery.
Hey, guys! I want to emulate Mac OS X 10.9 in my Moto X... Just a few questions:
1-I read that emulators are not virtual machines.. what's the difference between them?
2-There's an emulator/virtual machine for android that runs better and faster than Bochs?
3-There's an way to acess the internet and listen audio in the emulator?
Thank You and sorry about the english because i'm brazilian...
pedrocarboni said:
Hey, guys! I want to emulate Mac OS X 10.9 in my Moto X... Just a few questions:
1-I read that emulators are not virtual machines.. what's the difference between them?
Click to expand...
Click to collapse
You are correct in that they are different, but are very closely related. Emulators are programs that allow you to run programs from one CPU instruction set on another. For example, Intel and AMD CPU's run the x86 instruction set, while most phones and tablets use the ARM instruction set. An emulator will let you run x86 code on an ARM system, or the other way around. Unfortunately, other hardware has to have special support (video card, sound card, networking). It can also run x86 code on an x86 system. This is useful to run two operating systems on one computer at a type (such as Windows and Linux, MacOS and Windows, etc.).
A Virtual Machine is probably best explained by using the Java language as an example. When you write a Java program and compile it, it turns the readable code into something called "bytecode". Its similar to x86 and ARM in the sense that it breaks down instructions into the simplest possible form, however, its for a computer that doesn't exist, a "virtual" computer. The system is designed so a program called a "Virtual Machine" can easily run the instructions on any computer, no matter if its running on an x86 computer, or ARM computer, or is running Windows, Linux, MacOS, or Android.
2-There's an emulator/virtual machine for android that runs better and faster than Bochs?
Click to expand...
Click to collapse
Unfortunately I don't know. However, I think that most Android devices would have difficulty emulating MacOS since they have very limited CPU and RAM resources.
3-There's an way to acess the internet and listen audio in the emulator?
Click to expand...
Click to collapse
This depends on the emulator, but most definitely. For example, the Virtualbox x86 emulator provides devices to the emulated system to do just this.
Thank You and sorry about the english because i'm brazilian...
Click to expand...
Click to collapse
Your English is quite good. No need to apologize for it . I hope I was of some help.
nhakobian said:
You are correct in that they are different, but are very closely related. Emulators are programs that allow you to run programs from one CPU instruction set on another. For example, Intel and AMD CPU's run the x86 instruction set, while most phones and tablets use the ARM instruction set. An emulator will let you run x86 code on an ARM system, or the other way around. Unfortunately, other hardware has to have special support (video card, sound card, networking). It can also run x86 code on an x86 system. This is useful to run two operating systems on one computer at a type (such as Windows and Linux, MacOS and Windows, etc.).
A Virtual Machine is probably best explained by using the Java language as an example. When you write a Java program and compile it, it turns the readable code into something called "bytecode". Its similar to x86 and ARM in the sense that it breaks down instructions into the simplest possible form, however, its for a computer that doesn't exist, a "virtual" computer. The system is designed so a program called a "Virtual Machine" can easily run the instructions on any computer, no matter if its running on an x86 computer, or ARM computer, or is running Windows, Linux, MacOS, or Android.
Unfortunately I don't know. However, I think that most Android devices would have difficulty emulating MacOS since they have very limited CPU and RAM resources.
This depends on the emulator, but most definitely. For example, the Virtualbox x86 emulator provides devices to the emulated system to do just this.
Your English is quite good. No need to apologize for it . I hope I was of some help.
Click to expand...
Click to collapse
Hey guy! Thank you so much for the help! I thought it was the same thing...
Anyway, I already saw Bochs emulating Windows 7 without lag on the Samsung Galaxy S5..
Thank you!
hmmm....try limbo...
I have an app (ECUTalk) that can run on both Windows x86 and ARM (WinCE). I would think that this would be easy to port over to the Windows RT device. Anyone think this would be possible?
Globalrebel said:
I have an app (ECUTalk) that can run on both Windows x86 and ARM (WinCE). I would think that this would be easy to port over to the Windows RT device. Anyone think this would be possible?
Click to expand...
Click to collapse
Title is misleading.
There is a thread for port request.
It uses .net 1.x which is not exist on Windows RT, thus it can not run as-is (assuming it's a pure .net program).
No source code, no port.
WinCE and Windows are two totally different beasts. You won't ever be able to just run a WinCE app on Windows. It'll require a fair deal of reworking.
It might be possible to run ARM WinCE apps if someone ports the Shared Source Device Emulator 1.0 Microsoft has made. Though, I doubt it would be easy as that thing probably makes heavy use of x86 ASM.
You could likely use QEMU to run an x86 build of WinCE in emulation.
Another possible option would be to use the MESS emulator package. There is at least one driver that can boot Windows CE on an emulated ARM board.