Tag Archives: dual boot

Android-x86 KitKat 4.4.4 Build 10 with GAPPS, three new Windows launchers, Bluetooth (working!) and Mesa 10.5.9

Android-x86 KitKat 4.4.4 Exton Build 180108, version 10, is a ready!
This new version (180108) is basically the same as AndEX KitKat Build 160214. I have now upgraded some apps and added three new (Windows) launchersComputer Launcher, Microsoft Launcher and Win 10 Launcher. To be able to run AndEX Oreo 8.1, which was released 180103, you’ll have to use a fairly new computer. AndEX KitKat runs also on older computers, which is one reason for me to remind you of the existence of AndEX KitKat 4.4.4. I can mention that this KitKat Build 10 works on my (very) old Acer Aspire 5102WLMi AMD with ATI Radeon Xpress 1100. Many 3D games run just fine. So you can use AndEX KitKat Build 180108 to bring an old PC back to useful life! I mean a PC on which you have an old (perhaps outdated) Windows system installed.

Features
I’ve added Mesa (3D Graphics Library) 10.5.9 for better Graphic performance. The system can run live (from CD or a USB stick) on almost all laptops (and some Desktop computers). For example Acer (Aspire), HP, Samsung, Dell, Toshiba, Lenovo, Thinkpad, Fujitsu, Panasonic and Asus laptops. I can also mention that I could run this version without problems on a HP Pavilion 500-317no Desktop Computer. The Android system is distributed in the form of an ISO file as the rest of my Linux distributions. I.e. you must (as usual) burn the ISO file to a DVD if you want to run the system live on your computer or install it to hard drive. Read about how to burn ISO files. Or skip that. Just use ImgBurn. Nothing can go wrong. Or transfer the ISO file to a USB stick with Rufus and run the system live from the USB stick. You can easily install the system to your hard drive and install new apps. You can also install new apps while running the system live. Google Play Store and Aptoide App Manager are pre-installed so you can just make your choices…

Replacement
This version (version 10) replaces all my previous (9) Android-x86 4.4.4 KitKat builds. In version 10 (as in version 9) I’ve added GAPPS. I.e. Google Play Services, Google Play Store, Maps, YouTube and more apps. Everything just works.

What’s the point?

Well, if you like your Android phone and all the apps you have installed on it I’m sure you will also like to run apps from your laptop. Bigger screen and better sound etc. Read my article About how useful an Android-x86 system can be for the average computer user.

Need to upgrade?
Well, if you have installed any of my previous KitKat versions with GAPPS to your hard drive and the system is working alright you don’t “have to” upgrade. That’s because (as I say above) all included GAPPS will be upgraded automatically (just like your Android phone). Otherwise you can contact me so I can send you the new download link. Then please show your previous receipt.

SCREENSHOTS
1. Choosing launcher
2. Desktop with Computer Launcher
3. Running YouTube
4. Running in VirtualBox
5. Running in VMware
6. First screen – auto turn

READ MORE…

How To dual boot, triple boot or multiboot Linux with Windows in a simple way and be happy

In this instruction I will show you how easy it is to have several Linux systems installed on one computer together with for example Windows 10. The configuration is so simple a ten year old child can do it.

BACKGROUND
Ubuntu and all Linux systems based on Ubuntu (such as Linux Mint) uses Grub2 as boot manager. Also Debian and most other Linux systems use Grub2. Grub2 works differently from the old Grub Legacy.

UEFI BIOS and non-UEFI BIOS
The Extensible Firmware Interface (EFI) or its version 2.x variant, Unified EFI (UEFI) is a firmware type that is widespread on recent computers, especially those more recent than 2010Ubuntu wiki.

Configuring Grub2 – Example for non-UEFI BIOS computers
One of my computers, an Acer Aspire 5750G from 2010, has a 750 GB hard drive and an external USB hard drive of 1000 GB. On that computer I have Windows 10 and twelve (12) different Linux systems installed. Of those twelve systems three are Android-x86 systems (AndEX Nougat and AndEX Marshmallow).  Below I will describe step by step how I configured Grub2 in the easiest way possible.

1. The computer was delivered with Windows 7 (now updated to Windows 10) preinstalled on /dev/sda2 and /dev/sda3. I immediately started up my computer from a Linux Mint Live DVD. Using GParted, I created seven new partitions on the internal hard drive and three on the external USB hard drive. After that I installed Mint on /dev/sda7 and Grub2 on /dev/sda (MBR) at the same time as the installer also suggested. Then I restarted my computer and checked that Mint (and Windows) could be started. Everything worked (as expected) fine. See screenshots below showing how my partitioning looks like now.

The internal hard drive partitions
Note the 4 GB SWAP partition on /dev/sda6

The external USB drive partitions

2. Then it was time to install Arch Linux on /dev/sda8. When the installation prompted installation of Grub2 during installation, I chose to install Grub2 on /dev/sda8. Such an installation of Grub2 does not affect the existing Grub2 installation in MBR. I did it just the same to find out “start data” for Arch Linux. I then read these start data from Mint in the /mnt/sda8/boot/grub/grub.cfg file.

3. After that I started Mint on /dev/sda7 again. Now it was time to get a real “multiboot computer” using Grub2. This is how I did it:
A) In /etc/grub.d I deleted all files except 00_header, 05_debian_theme, 06_mint_theme, 40_custom and README. Said folder then looked like this.



B)
I edited the /etc/grub.d/40_custom file to look like this. Note that this is how my 40_custom file looks like now when I have installed totally twelve Linux systems. What I should write about the start of Arch Linux (see above) was already fixed by looking at the /mnt/sda8/boot/grub/grub.cfg file. I could do it in a similar way when I installed the other eleven Linux systems.

C) Finally, I ran the update-grub command. Then the /boot/grub/grub.cfg file (which is the file Grub2 “takes into account” at boot) was created/changed. This file (grub.cfg) should never be edited manually. Instead, edit the file 40_custom, as I showed above. Always use Leafpad or Mousepad (or a similar simple editor) when editing 40_custom. Never Libre Office Writer or Word or the like of them. Study my present grub.cfg file. When I now start up my Acer Aspire the boot screen look like this.

My BIOS settings on my Acer Aspire look like this.

Configuring Grub2 – Example for UEFI BIOS computers
On another computer (laptop) Lenovo Z50 from 2015 I have Windows 10 installed together with three Linux systems. Ubuntu 17.04 and two Android-x86 systems. Since Windows 10 was installed in UEFI mode I also had to install Ubuntu 17.04 in UEFI mode to be able to configure Grub2 the way I describe above. I went into BIOS and changed the settings to look like this.

When I went into the boot menu in BIOS I could choose my USB stick. In this case Kingston DataTraveler – watch this screenshot.

So I started up Ubuntu 17.04 from the USB stick and installed it on a partition I had created in advance using GParted.  Since my Lenovo already had a ESP (EFI System Partition) I installed Grub2 onto that partition. When I now start up my Lenovo the boot screen looks like this. (You can of course install many more Linux systems if you like. Just edit /etc/grub.d/40_custom the way I describe above).

IMPORTANT: Identifying if the computer boots the Ubuntu DVD/USB stick in UEFI mode
If the BIOS is set up to boot the DVD/USB stick in UEFI mode, then you will see the screen below.

If the BIOS is NOT set up to boot the CD in UEFI mode, or if the disk is not 64-bit, then you will see the screen below.


(ExTiX is based on Ubuntu)

Grub2 bootsplash
One of the benefits of Grub2 is that you can have a nice high resolution image as bootsplash/grub boot image. The image may have the same size as the resolution on your screen can handle, for example 1366×768. It is common with a regular image in jpg, png or tga format. Just place the image in /boot/grub and run the update-grub command. If you get the answer that the image is found in /boot/grub it will work. If not, try editing the /etc /default/grub file and add the line
GRUB_BACKGROUND = “/boot/grub/MyNicePicture.png”
Then run the update-grub command again (and restart the computer).

Have a look at my /etc/default/grub file.

Change the text – font and size – which Grub2 shows at boot

Run the following command:
grub-mkfont –output=/boot/grub/DejaVuSansMono.pf2 –size=24 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
(Maybe you’ll need to run the command (apt-get install ttf-dejavu first). Then edit the /etc/default/grub file and add the following line.
GRUB_FONT=/boot/grub/DejaVuSansMono.pf2
Run the update-grub command again. After rebooting, the Grub2 boot menu will surely look better (depending on how your boot image looks like).

Good luck!

/exton

Read about my Android-x86 Systems – Nougat, Marshmallow, Lollipop and KitKat at
andex.exton.net
– latest is AndEX Nougat!
and
about my Nougat, Marshmallow and Lollipop versions for Raspberry Pi 3/2 at
raspex.exton.se – latest is RaspAnd Nougat!