Related
Hi
Since a few days, I owned a new WeTab to play around with different tablet operating systems.
I'd like to install Windows 8, Android and Ubuntu in parallel and use the new GUI bootloader from Win8 to choose what to boot.
I started with installing Win8 and installed EasyBCD to modify the bootloader
A little test configuration shows the correct function of it.
When I start to intstall Android the fist time, everything was fine, but after installing ubunto the Windows 8 Bootloader turnd from GUI to text mode.
also
bootrec /fixmbr
bootrec /fixboot
common Win8DVD repairoptions
can switch back to GUI mode
is there a trick to get the GUI back, because without Keyboard on the tablet it's quite hard to select an option
Ad. Info:
WeTab with 80GB SSD, 2GB RAM
Partition:
sda1 ntfs 350MB Windows Bootloader
sda2 ntfs 20GB Windows Partition
sda3 ext2 200MB /boot for Ubuntu
sda4 extended partition
sda5 swap 4GB /swap for Ubuntu
sda6 ext4 20GB / for Ubuntu
sda7 ext3 4GB / for Android
I don't have multiboot set up on my device, but apparently, setting Windows 8 as the default system in the bootloader will bring back the GUI bootloader, as that actually doesn't reside in the MBR, but is loaded after some very early parts of Windows 8 (presumably touchscreen support).
I don't think the MS bootloader will support doing that, but I'm not posative.
I have a triple boot working fine right now though.(Win8, vista, Ubuntu)
I had vista and Ubuntu installed, I resized my vista partition and used the free space to create an ntfs part, then installed win to the new part(sda2) Sda1 still has the MBR though. After installing windows 8 I lost grub(bootloader), so I used a live disk to boot up and run boot-repair which is a nice GUI to simplify reinstalling the bootloader, and also to configure it.
I left grub to default to Linux though you can tell it to default to win if you like in the options.
Now at boot I get menu from grub which allows me to choose to boot to either sda1, sda2, etc. If I want Ubuntu I choose it from grub, if I want win I choose the partition vista is on(cause that is the place win8 put it's loader. Once I select vita partition my system loads the win loader GUI that lets me choose between vista and windows 8. I would think you can do the same with grub.
Sent from my A100 using XDA
NoSudo said:
I left grub to default to Linux though you can tell it to default to win if you like in the options.
Click to expand...
Click to collapse
you're missing the problem, without a GUI he cannot select a boot option because his tablet doesn't have an inbuilt keyboard!!
try installing windows and whatever else in a fashion that allows the GUI bootloader to stay, then install ubuntu to a partition but tell it to NOT install a bootloader, then try to setup "neogrub" from EasyBCD to boot it using the Windows 8 bootloader.
EDIT: in other words, don't add that "/boot" partition ubuntu loves so much, don't make an ubuntu boot partition, don't install grub, see if EasyBCD's Neogrub can work.
Thanks for the Reply's
I figured out that the light sensor on my tablet can be used as "Arrow Down"-Key so I'm able to use Texed based bootloaders.
However the Win8 GUI loader is nicer than the old school text based one. :-D
well, i had a quick look last night and you can indeed add the neogrub bootloader without losing the GUI loader, after installing neogrub using easyBCD you then just have to write a grub-ish bootscript that tells neogrub how to boot ubuntu, and then you can just touch Neogrub from the Gui bootloader and Neogrub will go straight to booting Ubuntu.
moved to general
I had the same problem and it got soleved by typing:
bcdboot C:\Windows
in an elevated command prompt, which will restore the default BCD settings for windows 8 and it will show the graphical GUI, you can then use bcdedit to do your required modifications because EasyBCD changes made me lose the GUI Boot...
Check this article for more info on restoring GUI Boot:
http://superuser.com/questions/4996...-8-gui-boot-loader-after-installing-windows-7
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Cran0g said:
Hi Folks,
Brand new ot the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
IRX120 said:
You might not have enough ram in your PC, try 512mb that's as low as you can go for 4.2
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hello,
I''m new as well and have exactly the same scenario on installing Eclipse on win 7 64 bits and try to learn with a Nexus 7 tablet.
I've tried adding the parameter to set 512mb but I'm still have the same problem. what else can be the problem ?
Thanks for any feedback.
Cran0g said:
Hi Folks,
Brand new to the forum (and, indeed, Android development). I have a Nexus 7, and I'm developing on Windows 7 using Eclipse. To try out the tutorials on the Android site, I attempted to follow their instructions to create a virtual Nexus 7 device. Seemed pretty straightforward. However, when I try to start the deveice, I get the error "Failed to allocate memory:8". It doesn't matter if I put 200 in the "SD Card Size" or select the SD card img file, I get the same message and the emulator is terminated by the application.
I have searched the archive on this forum but can't find anything close to this. Any ideas?
Click to expand...
Click to collapse
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
nexusnino said:
Did you solve this issue ?. I have exactly the same problem you have and I couldn't find any answer yet.
Thanks.
Click to expand...
Click to collapse
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Android Virtual Device Manager said:
On Windows, emulating RAM greater than 768M may fail depending on the system load. Try progressively smaller values of RAM if the emulator fails to launch
Click to expand...
Click to collapse
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
Starting Android Emulator said:
...Failed to allocate memory: 8...
Click to expand...
Click to collapse
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
bftb0 said:
There seems to be a bunch of things that the prior respondents never bothered mentioning
- What version of OS are you using on your PC? (also, 32-bit, or 64-bit?)
- How much RAM is in your PC?
- After you boot up your PC, and have a look with the Windows Task Manager, how much memory do you have in use with your PC sitting idle?
- What version of the Android Developement Tools do you have installed into Eclipse (v21.1 or above)?
- Does your processor have Intel/AMD Virtualization extension support?
- You are *not* attempting to run an emulator under an emulator (e.g. VirtualBox) are you?
- Which API Level and Device are you trying to run from the AVD?
I have a Win7 Pro x64 box, i5 quad-core uP w/ VT-X extensions, 4 GB RAM. When I create (for instance) an "API Level 17" Nexus 7 emulator, the AVD dialog complains:
Now, the default settings for a Nexus7/API 17 AVD device are 1024 MB RAM (just as with the physical device). When I attempt to run this way, sure enough I get a message
but when I edit that virtual machine to use 768 MB, it runs just fine.
Monitoring the physical memory in use:
Windows 7 Pro x64: ~1.0 GB
+ Eclipse (v3.6.2) + AVD : ~ 1.2 GB
+ 768 MB Emulator Running: ~1.7 GB.
I conclude that the "768 MB" limit is some strange interaction between the ADT and Windows - I routinely operate other VMs on my machine that use up to 2 GB of memory.
hope that helps.
Click to expand...
Click to collapse
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
nexusnino said:
=========================================
Thanks for the message; here are the answer to the questions you sent:
1- I have Windows 7 ( 64 bits)
2- 4 GB of Ram
3- When the computer just started and idle use 1.3Gb of Ram
4- I've installed ADT V 22.0.1 - 685705
5- I can't find how to check if the VT-x is enable or not
6- I don't use any kind of Virtual Machine on this computer
7- API level is set to 17, but not sure what you refer to Device or AVD
As an extra comment I have and Nexus 7 that is running 4.2.1, that eventually I would like to test the apps in there.
Thanks for your time and help.
Click to expand...
Click to collapse
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
bftb0 said:
@nexusnino
Your setup looks pretty close to mine. Win7/x64, 4 GB. Now that I think about it a little more, I'm not sure if the VT-X processor extensions matter for the emulator, as the Android emulator is an ARM instruction-set emulator, not a true x86 native instruction-set VM.
(In my case, I built my own machine; knowing that I was going to be using VMs a lot, I went through Intel's processor model comparison database and selected an processor model that supports the VM hardware extensions. Intel sells a lot of "i5", "i7" processor model variants. In your case, you would need to find out the exact processor model in your PC to figure out if it has Intel VT-X or AMD/V. But, as I mention above, I'm not certain it is relevant to the Android emulators).
In the AVD (Android Virtual Device) v21.1, when I select Nexus 7, it pre-populates the VM RAM/Heap settings. If I leave RAM at 1024 MB, I get the error 8 message. But if I adjust the VM RAM size downward (e.g. 768 MB), the VM starts correctly. I didn't try other values - the /!\ caution message seems to indicate that other values, possibly higher, might work.
I just updated my ADT (and eclipse plugins) to 22.0.
Same deal on v22.0 as on v21.0 - the emulator errors out (error:8) if I leave the RAM set to 1024, but if I drop it to 768, it starts up just fine.
see attachment image
What happens if you drop the RAM settings down?
Click to expand...
Click to collapse
Thanks very much for the very detail post; I've adjust to 768 and I can consistently run without getting the error back.
Much appreciate your time and help.
Paulo
i have a problem
i had windows 8.1 64-bit in my pc then after that i installed windows 8 32-bit in different partition after that when i reboot my pc i didn't get the dual boot option to choose between windows 8 and 8.1..my system automatically loads windows 8....
Sounds like you didn't do the installation safely with regard to the old OS. The 64-bit one may have been using a 64-bit bootloader? In any case, you may have clobbered the boot partition of the old installation. You can try using bcdedit to add a boot entry for the old OS - it might still work - but you may need top use 64-bit Win8.1 recovery media instead (and doing so you risk clobbering the boot partition for the 32-bit install).
... Do I dare ask why somebody would *do* this? I mean, I could understand if you were installing Win7 or something, and even vaguely understand why you'd install 32-bit instead of 64-bit (though these days I pretty much exclusively use virtual machines for 32-bit systems) but why in the world install 32-bit Win8 on a 64-bit Win8.1 machine??
Let me preface that ever since I heard of an Intel based phone, the idea of running Windows at near native speeds has always intrigued me.
It's not perfect, but I think we're very close to that goal
Here's a video of my ZE551 running Windows 7:
Edit:
Here's @knightmare running Windoze 10 on his ZF2
http://forum.xda-developers.com/showpost.php?p=62008697&postcount=144
Edit:
Here's a video of my ZE551 installing Windoze 8: ( pretty boring for most people since it's just the install )
Edit:
Here's a video of my ZE551 playing ( I use that term loosely here ) a D3D9 game: Runes of Magic. Even though the Windows 8 QXL driver says it's hardware enabled in DxDiag, it's painfully slow.. taking nearly 15 minutes to start up/log in.
Edit:
Here's a video of Passmark 8 on Windows 8. Some people asked for benchmarks:
Here are the tools you will need to get this running yourself ( ZE551 ):
1. KVM enabled kernel - http://forum.xda-developers.com/zen...fhd-kernel-ze551-kvm-bridge-compiled-t3145055
2. Linux chroot - the one I use is called Linux Deploy ( in the Play Store )
3. Spice client - the one I use is called aSPICE ( in the Play Store )
4. Root - kinda duh
5. Unlocked Bootloader - without an unlocked bootloader, you can't install a new kernel
6. Terminal Emulator - the one I use is called Terminal Emulator ( in the Play Store )
7. SSH client - the one I use is called VX ConnectBot ( in the Play Store )
8. Busybox - most every root-based app uses this ( in the Play Store )
9. OS iso - any cdrom image of the OS you want to run, ie windows 7?
Optional:
1. (optional) a decent sized MicroSD card, I use a 128 gb one that's partitioned 50 gigs or so as ext4 for Linux & 70'ish gigs for vFAT
2. (optional) an SD Card partitioner - the one I use is called Aparted ( in the Play Store )
After unlocking your bootloader and getting root running, this is the process you will follow:
1. Flash the 2.19 kernel img using fastboot flash boot boot_2.19_kvm_bridge.img and reboot. Pray you boot up.
2. Start Terminal Emulator
2a. at the $ prompt, type: su
2b. Grant Permission to Terminal Emulator for Root access ( 1 time thing )
2c. check to see if kvm.ko and kvm-intel.ko are loaded by typing: lsmod
2d. If they aren't loaded, load them using the commands: insmod /lib/modules/kvm.ko and insmod /lib/modules/kvm-intel.ko
2e. exit out of Terminal Emulator by tying the command: exit and then exit again
3. Partition your microSD card using Aparted * OPTIONAL *
4. Use Linux Deploy to install your favorite Linux distro. Unless you are hoping to compile the Android AOSP kernel ( what the FHD phone kernel is ), you can use just about any of them. ONLY use SSH, you won't need framebuffer or X access. This could take upwards of half an hour.
5. After Linux Deploy has installed your linux distro, click Start to start up the chroot.
6. Use an SSH client to connect to your linux distro. ( I prefer to ssh in via my laptop, but also use VX ConnectBot when I'm out and about )
7. Use the package manager to install qemu-kvm for your distro. Most Debian & Ubuntu distros use apt-get, Arch uses pacman, Fedora uses rpm, etc...
7a. (optional) I find it easier to grant superuser privileges to my qemu-kvm executable, so I chmod a+s /usr/bin/qemu-system-x86_64 ; if you are paranoid about security, read through the documentation to do this correctly
8. I recommend creating a shell script to start up qemu-kvm because it can be a pain in the butt to remember all of the switches you like. ie...
qemu-system-x86_64 -full-screen -m 1G -enable-kvm -cpu host \
-drive file=/mnt/0/machine1.img,format=raw -boot menu=on \
--usbdevice tablet -smp 4 -vga qxl -monitor stdio -balloon virtio \
-soundhw hda -net nic,model=virtio \
-net user,smb=/mnt/MicroSD \
-spice port=5900,addr=127.0.0.1,disable-ticketing [email protected]
I have this line ( it's broken up by \'s <-- MAKE SURE THERE IS NO WHITE SPACE AFTER THE \ ) in my bash script called start_win7.sh
Here's a quick explanation of the line:
8a. qemu-system-x86_64 - This is the name of the qemu-kvm executable on my Arch x86_64 distro
8b. -full-screen - Full screen
8c. -m 1G - 1 gig of ram for our virtual machine
8d. -enable-kvm - enable KVM, the whole point of this endeavor
8e. -cpu host - use the same cpu information as our ZF2
8f. -drive file=/mnt/0/machine1.img,format=raw - the location of my hard drive, this is a 10 gig file
8g. -boot menu=on - boot menu enabled ( hit F12 etc.. )
8h. -usbdevice tablet - Qemu SUCKS at tracking the mouse, this forces qemu to track where we touch the screen
8i. -smp 4 - we're using 4 threads ( cores )
8j. -vga qxl - we're using the qxl vga adapter
8l. -monitor stdio - allow us to use the console to make immediate changes to the VM
8m. -balloon virtio - use the virtio balloon feature in the KVM kernel
8n. -soundhw hda - use the Intel HD Audio driver for sound
8o. -net nic,model=virtio - create a network card using the virtual IO feature in the KVM kernel
8p. -net user,smb=/mnt/MicroSD - create a shared folder, in this case the vFAT portion of the microSD card
8q. -spice port=5900,addr=127.0.0.1,disable-ticketing - Start up the SPICE engine for passing video & audio
8r. [email protected] - pass any further arguments to our qemu-kvm executable
so my file: start_win7.sh looks like this:
#!/bin/bash
qemu-system-x86_64 -full-screen -m 1G -enable-kvm -cpu host \
-drive file=/mnt/0/machine1.img,format=raw -boot menu=on \
--usbdevice tablet -smp 4 -vga qxl -monitor stdio -balloon virtio \
-soundhw hda -net nic,model=virtio \
-net user,smb=/mnt/MicroSD \
-spice port=5900,addr=127.0.0.1,disable-ticketing [email protected]
8s. chmod +x start_win7.sh to make it executable
9. Start up the qemu-kvm virtual machine referencing the location of your windows 7 install cd. ie...
./start_win7.sh -cdrom /mnt/MicroSD/Vcd/en_windows7.iso
9a. Qemu will start up and then show you this:
QEMU 2.3.0 monitor - type 'help' for more information
(qemu)
9b. you can then issue QEMU commands from the (qemu) prompt
10. Start up aSPICE
11. Click the OFF button to the left of Show Advanced Settings
12. Make sure Enable Sound is checked, if it isn't, do so.
13. The default connection is 127.0.0.1:5900, so click Connect
At this point, you should see your Windows install starting.
After this you will need the virtio drivers for your Windows box. I'll try to get those urls, but you should be able to Google them. Redhat has VirtIO & Spice guest driver cd's for Windows.
Redhat Windows Virtio Drivers CD: https://fedoraproject.org/wiki/Windows_Virtio_Drivers
SPICE Guest Drivers: http://www.spice-space.org/download.html ( download the QXL Driver and Spice Agent, the executable does not work )
Windows 8 QXL Drivers from Red Hat People: http://people.redhat.com/~vrozenfe/qxlwddm/
How to connect to Windows via RDP: http://forum.xda-developers.com/showpost.php?p=62096457&postcount=165
Edit:
Verified that Windows 8.1 pro can be upgraded to Windows 10. Redhat's qxl windows 8 driver works with Windows 10.
Great job bro. This is iam waiting for using zenfone 2.Is there any sound for windows 7?
if like can i change into windows 8 or 10??.
Tq
Yes, there is sound using aspice if you use the Intel hd audio driver. Unfortunately, the pc link video grabber doesn't record sound. ( why there isn't audio in my video )
Since this virtual machine is simply a pc, you should be able to install Windows 8 or 10.
Please let us know how that turns out!
Sent from my ASUS_Z00AD using XDA Free mobile app
this is amazing...this means there is a chance in the future, to run windows 10 or windows phone 10 (whenever that comes out) ? what about connecting mouse/keyboards via bluetooth? i cant wait for this to grow more! amazing work...!!!
Amazing! Care to try with Windows 10 to see how it behaves?
Seems already fast in your video, you already have ideas to make closer to native speed or it's already the best?
You've outdone yourself. A full modern Windows desktop OS in our pockets.
@ycavan
The very important question: What about video driver? Is it just dummy SVGA or full featured 3D graphics card?
Without Direct3D, windows for me will be nearly useless.
At the moment there is no direct 3d. The problem there is that my chroot doesn't seem to have proper access to all the hardware.
I've heard that the vmware driver is supposed to support d3d9 natively via gallium.
So... The next step would be to look at getting qemu-kvm compile for Android.
If any awesome Android developers out there are willing to do that, we might have a chance at full speed Windows with direct 3d.
I will say this... Epsxe was able to start up ps1 games with Pete's opengl driver via spice.
Sent from my ASUS_Z00AD using XDA Free mobile app
I've been messing around with the Android NDK lately, and if I have time today, I can try cross-compiling qemu-kvm.
This type of stuff is why I love supporting the XDA Community. Very cool. I'll give it a shot today - if USB OTG works, I'll have to see if I can get my Tactrix OpenPort cable to work with it and MazdaEdit.
This is a wonderful job bro... Can we follow the same procedure on other phones (Oneplus One in my case) with a kernel that supports KVM?
vigneshnallamad said:
This is a wonderful job bro... Can we follow the same procedure on other phones (Oneplus One in my case) with a kernel that supports KVM?
Click to expand...
Click to collapse
Since the Oneplus One is using an ARM based chip , not a x86 chip so I don't think it's possible to run Windows
damn man, that's some awesome stuff right there. imma have to find me self a zenfone 2
Jay.Lent said:
damn man, that's some awesome stuff right there. imma have to find me self a zenfone 2
Click to expand...
Click to collapse
Do it. Peer pressure!
awesome work Bro..
btw will it increases battery life of zenfone 2? or making it worse?
as we all know that android 5.0 is very buggy, the memory leak problem cause battery draining, so I wonder about your trick by installing windows 7 on asus zenfone 2 will it fix the battery draining problem?
Awesome Work !! Wish you all the very best for future developments
Wow excellent job.:thumbup:..didn't except such a beautiful stuff....lol touch screen Windows 7
Sent from my ASUS_Z00AD using XDA Free mobile app
Oh my glob! If there is any possibility to have tf2 in my pocket... I will seriously throw money at someone.
qkall said:
Oh my glob! If there is any possibility to have tf2 in my pocket... I will seriously throw money at someone.
Click to expand...
Click to collapse
You could always stream it from your PC as I'm not certain it would run well even on minimum settings.
As per the fact that the windows 7 runs on VM inside the Android, it should ideally worsen the battery life. Windows 7 doesn't replace the android os. If someone is worried about battery should not try this. Nevertheless, it truly would be a great thing to witness.
Hello everyone. I was using Windows 10 for Android Development but I switched to Hackintosh and I saw up to 80% improvement in compiling times. I can assume that JVM on Windows is different that macOS-Linux. So, what if you install JDK on Ubuntu bash in Windows 10 and make it primary JDK on Android Studio? Anyone tried this?
For the record my PC components are:
Intel i3-6098P
Nvidia GTX260 Core 216
Asus H110MA/M2
Corsair Vengeance 8GB