Drivers Exopc



ExoPC/WeTab with Android booting

Downnload ExoPC C150 laptop drivers or install DriverPack Solution software for driver update. Install ExoPC Smart R8-CE laptop drivers for Windows 7 x64, or download DriverPack Solution software for automatic drivers intallation and update.

The official Android project only releases versions for the ARM platform, but there is an unofficial porting project for the Intel x86 platform called Android-x86. Using this version you can in theory install Android on any home computer lying around. In practice however you need to consider what kind of components your device has and if they have suitable Linux and Android drivers available.

Luckily if one of your excess computers that you have lying around is an ExoPC (WeTab), there is an ready made “ExoPC adaptation” available that is pretty complete and supports everything from screen light sensor to wireless connection and rotation detection. Here is how to install it.

First download the AndroidICS_for_Wetab_CorvusMod_finalRelease.iso file and then put the image on a USB stick using the command below, replacing sdb with your actual USB device name.

The insert the USB key into you ExoPC and while it boots, press the BBS icon to access the BIOS boot menu. Using the upper left hand circle button, press single presses to select the external USB key and long press to activate the selection so that is boots.

From there on you can follow the installation instructions at the Android-x86 site, although if you have experience installing any OS, you probably don’t need to read any instructions. When the installer asks if you want to have a fake 2GB SD card, you should answer yes.

Dual-boot

If you want to preserve the previous OS you had on the device, you can do that and dual boot. The Android installer has full support for partition management. The booting is done with Grub, and the installation of Grub even automatically detects other operating systems, so setting up an dual boot is very easy. In the rare case that you need to tweak Grub settings, you can boot using the Grub option Android debug mode and edit the config file with command

Press ‘i’ to get into edit mode, make your modifications and to save and exit in Vi, press ‘Esc’ and then ‘ZZ’ (capital z, twice).

When you are done with the installer, just reboot without the USB stick and you will boot into a fully working Android system. Compared to Mer/Nemo UI, Ubuntu 12.04 or OpenSUSE 12.2 with Gnome 3.4, the Android 4.0.3 Ice Cream Sandwitch provides the fastest and most complete touch friendly experience. This is something you can really use on daily basis to read e-mail, watch TED videos or browse websites.

Drivers exclusion

Apps and features not on the level of a full Linux system

Unfortunately not all Android apps in Google Play are available for the x86 platform, most notably Adobe Flash is available only for ARM platforms. Intel has been working on an ARM translator, so this might change in the future.

To my knowledge Android does not have a usable LibreOffice port yet or any other decent OpenDocument word processor or spreadsheet editor, nor is there a good plain text code editor, so dual booting to a full featured Linux distribution is necessary to get any actual work stuff done. Android also lacks comprehensive disk encryption and real multi-user support, so that might be an limiting factor for some.

There are however a range of apps that try to fix some of these limitations. For example SwitchMe emulates traditional multi-user features available in other Linux distros. Also the F-Droid provides an easy way to browse, install and update open source Android apps.

Drivers Exopc Lbp

ExoPC/WeTab with Android booting
ExoPC/WeTab with Android and Angry Birds
ExoPC with Android in portrait mode

We are living interesting time as there is so much competition in the mobile space now. Let’s see how Android and it’s competitors develop, it’s certainly not too late even for new players to enter the game..

Hi folks, Long time no see. So I've put away the WeTab almost for good but then a couple of days ago I got to thinking it could be a nice central system to just spend a few minutes maybe browsing around some cooking videos on youtube in the kitchen. So I got up to my tinkering business again and whaddya know I actually learned something new in the process.
First off I downloaded the latest release of the Android X86 distro which looks like it's some port of the cyanogenmod system.
So previously I had mentioned in some install blog that with USB sticks it is a hit or miss...well apparently it is nothing physical, it's actually just a silly magic set of bytes that needs to be written someplace on the USB stick. I found this out when I started getting an Error 17 (or was it Error 7, I forget). In any case, according to these nice people at the WeTab community the USB stick needs to have that written somewhere in the first 400 bytes or so.
I finally managed to write the code on to the stick but not with the printf examples I found on-line.
Instead I opened up Hexfiend and created a file with the sole 4 bytes I needed: 9d 2a 44 7b
I named the file test.bin and then used dd to write the code where it has to go.
I'm not sure if I was just running into some silliness on my part but I was doing this on a mac and apparently there are two ways to refer to the physical device, either raw by /dev/rdisk2 or some other layered way with /dev/disk2.

Drivers Exopc Taylormade

Of course this needs to be done only after you've figured out what the proper path is to your USB stick by running
Testhdutil list
Anyhow, once you have that test.bin file created, you can then DD it to the write spot on the USB stick boot record.
sudo dd if=test.bin of=/dev/disk2 bs=1 seek=440
Use hexdump then to ensure that you see those 4 bytes where they ought to have gone:
sudo hexdump -s 440 -n 4 /dev/disk2

Drivers Exopc Golf Clubs


Drivers Expense

First impression is I like this better than Windows on the WeTab because of the lesser performance hit. But it looks like the video rendering drivers are whacked. I still have to look around a bit to see if that's something that can easily be fixed with some boot setting. Well, enough tinkering for now, enjoy cracking open your old junk closet and digging the WeTab out :)Drivers

Drivers Exopc 64