Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,780,683 Members 51,188 Now Online
XDA Developers Android and Mobile Development Forum

Exe files on Android?

Tip us?
 
2Noob4U
Old
#1  
2Noob4U's Avatar
Senior Member - OP
Thanks Meter 13
Posts: 184
Join Date: Sep 2009
Location: Pueblo, CO
Default Exe files on Android?

This might be in another thread. I searched pretty extensively for an answer and can't find one. Is there an app or way to install exe files and run them on my Magic 32B? My phone is rooted and running Cyanogen's 4.2.5 I figured my phone does everything else, why shouldn't it be able to run exe files?
The Following User Says Thank You to 2Noob4U For This Useful Post: [ Click to Expand ]
 
2Noob4U
Old
#2  
2Noob4U's Avatar
Senior Member - OP
Thanks Meter 13
Posts: 184
Join Date: Sep 2009
Location: Pueblo, CO
Sorry for the bump. I can access the exe file on my memory card with Linda File manager, but I don't know what the open the file with??? Linda File Manager gives me the option to > Open With... Any ideas?
 
shoemeistah
Old
#3  
shoemeistah's Avatar
Senior Member
Thanks Meter 10
Posts: 312
Join Date: Jul 2009
Location: Netherlands, The
Android cannot open Windows based files.......
Android phones owned: HTC Magic G2, HTC Desire, Samsung Galaxy S, HTC Desire Z, HTC One X.

 
arock169
Old
#4  
Junior Member
Thanks Meter 1
Posts: 10
Join Date: Jul 2008
Default WEAK!

One thing I have learned from xda is that if theres a will theres a way! Comon guys there has gotta be a way!
The Following User Says Thank You to arock169 For This Useful Post: [ Click to Expand ]
 
tvall
Old
#5  
tvall's Avatar
Senior Member
Thanks Meter 800
Posts: 2,186
Join Date: Oct 2010
Location: Springfield
Android is not windows..
In theory you could port qemu or something and run it in that. But that would be so slow a turtle would think of itself as fast if it saw it

Sent from my Gingerbread on Sapphire using XDA Premium App
my work
optimus v:
iho magpie

dream/sapphire:
DREAMTeam Froyo, United ICS, and tvall's cm7

misc:
the first chromecast system image without bootloader updates or auto updating - obsolete

If you'd like to donate to me, i accept bitcoins and electronics
BTC - 1titsVyrUw8pGEDF6Jqdh56cZjBRYAQjQ
 
DonJuan692006
Old
#6  
Senior Member
Thanks Meter 162
Posts: 1,591
Join Date: Jul 2010
Location: Suffolk, VA

 
DONATE TO ME
Quote:
Originally Posted by tvall View Post
Android is not windows..
In theory you could port qemu or something and run it in that. But that would be so slow a turtle would think of itself as fast if it saw it

Sent from my Gingerbread on Sapphire using XDA Premium App
Agreed. I want to say someone got Wine to install in Android but could never get it to work right.

Sent from my LG-P500 using Tapatalk
Samsung Galaxy S4 16GB, Verizon
Current ROM: Gummy 1.1

Click me to root your myTouch 1.2/Fender (3.5mm jack) the old school way.
Click me to root your myTouch (regardless of version) the new school way.

If I've helped you out and you're grateful, buy me a Redbull. (Not a beer fan )


 
mumilover
Old
#7  
Senior Member
Thanks Meter 625
Posts: 1,270
Join Date: Mar 2010
Location: Copenhagen

 
DONATE TO ME
The idea is sweet and innocent but is much more complex...
The "exe" files are binaries. The .exe extension is something windows has as a standard for postfix, and is not necessary for running binaries (linux does not use any postfix and therefor also Android).
So what is a binary?
It's a list of machine instructions which the intended cpu understands. Every cpu has it's own instruction set ( a language). You need to make sure that the list of instructions you are running can be understood by the cpu. Inside this list you will find special instructions which is called "system calls". They are not intended for the cpu but for the operation system which you are running on.
So to sum up;
1) to run windows binaries on Android you need to change to instruction set of the binary because the cpu you have is not the same as those running on the Android device. E.g. x86 cpu on computer vs. ARM cpu on mobile devices vs. PIC micro-controllers. So the binary does not speak the same language as the cpu.
2) You need to change the system calls because Windows and Android does not have the same system calls.

So as a final sum up, it's not easy to make those binaries to run on Android, specially those which has a instructions list bigger than 20-30 instructions... They are just to complex and sometimes not even possible!

The WINE project is shot of doing the exact problem. It will run the binaries and translate them on the fly for the operating system. It succeed most times and fail others. But it's a HUGE project and need a normal computer power for it to run. The devices we have right now, does not have the horse power to run such projects.

I hope the info shades some lights on the problem :0)

NB: i know some of the info is not 100% but it's REALLY simplified to give the general idea and complexity of the problem :0)
If I was helpful or you liked my tools, please remember to DONATE and/or hit that "Thanks" button.
APK(s) Installer tool
HTC Magic: 4 easy steps ROOT guide
Fastboot Commander v.1.51
Fastboot Commander(HTC magic version)
The Following 2 Users Say Thank You to mumilover For This Useful Post: [ Click to Expand ]
 
K3n H1mur4
Old
#8  
K3n H1mur4's Avatar
Senior Member
Thanks Meter 112
Posts: 382
Join Date: Apr 2009
Location: Fortaleza

 
DONATE TO ME
Quote:
Originally Posted by mumilover View Post
The idea is sweet and innocent but is much more complex...
The "exe" files are binaries. The .exe extension is something windows has as a standard for postfix, and is not necessary for running binaries (linux does not use any postfix and therefor also Android).
So what is a binary?
It's a list of machine instructions which the intended cpu understands. Every cpu has it's own instruction set ( a language). You need to make sure that the list of instructions you are running can be understood by the cpu. Inside this list you will find special instructions which is called "system calls". They are not intended for the cpu but for the operation system which you are running on.
So to sum up;
1) to run windows binaries on Android you need to change to instruction set of the binary because the cpu you have is not the same as those running on the Android device. E.g. x86 cpu on computer vs. ARM cpu on mobile devices vs. PIC micro-controllers. So the binary does not speak the same language as the cpu.
2) You need to change the system calls because Windows and Android does not have the same system calls.

So as a final sum up, it's not easy to make those binaries to run on Android, specially those which has a instructions list bigger than 20-30 instructions... They are just to complex and sometimes not even possible!

The WINE project is shot of doing the exact problem. It will run the binaries and translate them on the fly for the operating system. It succeed most times and fail others. But it's a HUGE project and need a normal computer power for it to run. The devices we have right now, does not have the horse power to run such projects.

I hope the info shades some lights on the problem :0)

NB: i know some of the info is not 100% but it's REALLY simplified to give the general idea and complexity of the problem :0)
Just in addition, most programs aren't just based on the .exe file. DLLs and other files are needed for the program to run, attempting to port all this stuff to Android would most probably result in failing.
QTEK A9100
Sold

HTC Magic
Sold

Motorola Defy
Dead

Samsung Galaxy 5
Sold

Sony XPeria S
NAND: Carbon

Motorola Moto G
NAND: Carbon

Gathering money for a tablet
 
Wing Nut
Old
#9  
Wing Nut's Avatar
Senior Member
Thanks Meter 1
Posts: 201
Join Date: May 2009
Location: Adelaide
Quote:
Originally Posted by K3n H1mur4 View Post
Just in addition, most programs aren't just based on the .exe file. DLLs and other files are needed for the program to run, attempting to port all this stuff to Android would most probably result in failing.
I just hope Android is so popular that, like turning Windows into Linux using Wine (excuse the metaphor or whatever that was), someone might persist with this no doubt huge endeavour. I'm sure I'm not alone in wanting to never run a Windows app in Windows ever again, nor kowtow to Apple's interface demands even though I'd like something as responsive, integrated and occasionally useful as an iSomething.

Android was my future salvation till my employer handed over a handy Win App recently that I can't really avoid using - well I could, but I'd have to work that much harder - fat chance! So I'm stuck with a Samsung XP netbook and WM6.5 on my HTC Touch HD until someone somewhere, or lots of someones everywhere, do a Wine for Android
SGN2 N7105T and Touch HD (BLACKSTONE) T8285 with
ROM: EnergyROM (Recovering Flash Addict!) WM 6.5 (Leo) OS: 6.5 (5.2.21877) Radio: 1.17.25.09 Protocol: 52.69.25.37U
 
cellsafemode
Old
#10  
cellsafemode's Avatar
Senior Member
Thanks Meter 866
Posts: 591
Join Date: Apr 2011
Seriously, you want to pretend in some reality somewhere that someone will first create an x86 emulator for an arm chip that barely likes to play xvid files then on top of that use wine to run a mobile windows app rather than just use something similar or pay someone to write you something similar that runs natively on android?

Which do you think is the non-insane option?

The Following User Says Thank You to cellsafemode For This Useful Post: [ Click to Expand ]
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes