• Home
  • Reviews
  • Featured
  • Archives
  • Videos
  • Devices
  • Tegra
  • Send Tips
  • Contact
  • AndroidCommunity on Twitter AndroidCommunity on Facebook AndroidCommunity on Google+ AndroidCommunity RSS Feed

Android Community

    • MUST READ

      STORIES

    • Android 4.3 leaks on video with new camera UI

      May 24, 2013

    • HTC One ‘Senseless Edition’ could arrive this summer

      May 23, 2013

    • Verizon HTC One reality returns as DROID DNA offer pops up

      May 20, 2013

  • Trending Topics
  • Jelly Bean
  • NVIDIA
  • Galaxy S 4
  • HTC One
  • Nexus 7
  • Sell Your Used Phone

WindowsAndroid puts Android on your Windows machine without emulation

7
  • By Eric Abent
  • on 28 Jan, 2013

WindowsAndroid puts Android on your Windows machine without emulation

If you’ve encountered an Android app you wanted to have on your PC, then we’ve got some encouraging news for you. The folks over at Socketeq have released a piece of software they’re appropriately calling WindowsAndroid. The biggest draw of WindowsAndroid is that it runs Android natively on your Windows machine, meaning that there’s no need for emulation.

WindowsAndroid2wtmk

This, in turn, means a number of happy things, most importantly faster speeds. The reason there’s no emulation needed is because WindowsAndroid runs on the Windows kernel, instead of the Linux kernel. You’ll be working with Android 4.0.3 with this version of WindowsAndroid, so don’t expect to be rocking Jelly Bean on your machine just yet.

At this point, WindowsAndroid should play nicely with Windows Vista, Windows 7, and Windows 8, so if you’re using any of those versions, there’s a pretty good chance you can start running Android on your machine. You’ll have support for a mouse and keyboard with WindowsAndroid, so no worries there, while those of you with a new touchscreen Windows 8 computer should find that touch controls work as well. Obviously, since this is an early release, don’t be surprised if you encounter a few bugs and crashes as you’re using it.

WindowsAndroidwtmk

Normally, you’d be able to download WindowsAndroid from Socketeq’s website, but at the moment, the site is understandably experiencing some heavy loads. Socketeq has posted a number of mirror links in a Reddit thread about WindowsAndroid, so checking those certainly isn’t a bad idea. You’ll also want to snag a copy of Gapps if you want to play around with Google‘s Android apps. As always, download and install this at your own risk, and Android Community can’t be held responsible if something goes haywire with your computer. Are you going to give WindowsAndroid a spin?

WindowsAndroid2wtmk
windowsandroid3wtmk
WindowsAndroid4wtmk

WindowsAndroid5wtmk
WindowsAndroid6wtmk
WindowsAndroidwtmk


[via Android Police]
Share
  • Samsung Galaxy Note 3 with Android 4.3 spotted in benchmark results
  • Verizon HTC One "will be announced later"
  • New Nexus 7 reportedly shipping now, launching next month

Tags: Googlewindowswindows 7Windows 8

  • riv359

    Nice…

  • Scott Norcross

    anyone know how to install the gapps package for this ? lol its definitely not like flashing a phone

  • Anon

    crashed the dev’s site

  • Perry

    i unzipped it and put the stuff from the system folder into C:SocketeQwindowsandroid_rootsystem

    But only a few apps in app store, and mostly payed ones.

    Check this link to reddit…there is a lot of info.

    http://www.reddit.com/r/Android/comments/1773hv/android_403_ported_to_windows_78_natively/c82u7it

    Have fun
    Perry

  • carlos gómez

    what about users of Windows XP ?

    • philnolan3d

      Get with the times.

  • mdalvecchio

    Installed on win7 but not even strting with the following error:

    C:>android.exe

    OSALSockMap::init: sock_map=0x003A0000

    start /SocketeQ/windowsandroid_root//system/bin/plogd … 7352

    C:>start /SocketeQ/windowsandroid_root//system/bin/socketbinder … 9816

    add (socketbinder, 0) to sockmap ok

    start /SocketeQ/windowsandroid_root//system/bin/servicemanager … 1372

    [ on init ]

    [ on boot ]

    [ service netd ]

    [ service vold ]

    [ service surfaceflinger ]

    [ service ril-daemon ]

    [ service zygote ]

    [ service media ]

    [ service drm ]

    [ service installd ]

    reference-ril requires: -p or -d /dev/tty_device

    android-start was killed

    app_process was killed

    servicemanager was killed

    socketbinder was killed

    mediaserver was killed

    surfaceflinger was killed

    instld was killed

    no process ‘alogd’ was killed

    plogd was killed

    netd was killed

    vold was killed

    no process ‘bootanimation’ was killed

    rild was killed

    no process ‘drmserver’ was killed

    ——————
    Any suggestion?

    Thanks, m.dalvecchio@gmail.com

  • Search

  • REVIEWS

    • AT&T LG Optimus G Pro ReviewAT&T LG Optimus G Pro Review
    • Iron Man 3 game Review: what you need to knowIron Man 3 game Review: what you need to know
    • Samsung GALAXY S 4 ReviewSamsung GALAXY S 4 Review
    • Samsung Galaxy Note 8.0 ReviewSamsung Galaxy Note 8.0 Review
    • Pebble review: Two weeks with a smartwatchPebble review: Two weeks with a smartwatch
  • HANDS-ON & QUICK LOOKS

    • Coolpad Quattro II 4G and 8920 hands-onCoolpad Quattro II 4G and 8920 hands-on
    • Kyocera Hydro XTRM and EDGE hands-onKyocera Hydro XTRM and EDGE hands-on
    • Opera for Android exits beta, we go hands onOpera for Android exits beta, we go hands on


  • T-Mobile G1 Accessories
  • RECENT COMMENTS

  • About
  • Contact
  • Terms of Use
  • Privacy Policy
  • Advertise

Copyright 2013 Android Community