Has any been able to get their new X86 board with Wifi/Bluetooth module to work with android-x86_64-6.0-r3 OS? I know the module works with Ubuntu and Window 10 but no luck with Android.
I faced the same issue. Another problem is the screen orientation... I installed an app which runs only in portait but my desktop screen doesn't turn Does anyone know how to turn back the screen in landscape mode ?
There is a gyroscope/accelerometer on board so I would suggest to turn the Udoo X86 and it will flip the screen. Just kidding... Isn't there a Android X86 forum out there? This has nothing to do with Udoo hardware. Other people running Android on PC hardware should have the same issues I suppose.
@Guiz, I don't seem to have the same issue. My 24 inch HDMI monitor is in landscape orientation and when I installed OS' the desktop came up in Landscape.
There is now also Android X86 - BlissRom with working M2 Wifi/BT. For download see: https://www.udoo.org/docs-x86/Software_&_OS_Distro/Android.html
I would like to get a few testers for some Udoo-x86 specific builds of Bliss-x86. I'm still getting used to this form of development with hardware combinations that aren't too widely supported, but I've come a long way recently, and working together, we could possibly get it all working right for the Udoo-x86. Message me or find me on Google
Dear waltervl I tried installing in the internal 32GB EMMC Bliss Android bliss_android_x86_64 from USB key in legacy boot mode and it install but did not boot (single white line and black screen). Must I start from EFI? In legacy I tried either to install the Bliss Android GRUB and not to install it and to run the update-grub of Debian 9.0.1 installed on M2 disk but hoping to use it but does not recognize the Bliss Android installation. In Debian 9.0.1 installed in the M2 disk I can mount correctly the internal 32GB EMMC and look the files installed by Bliss Android but I can't boot it. Thanks in advance.
I personally have no experience with Android on Udoo X86 (nor plans to get involved, 1 OS is enough for me). Perhaps @Jon West could answer your question as he is involved in the development of Bliss-X86
Dear waltervl thanks for your answer. Please I want to know from @Jon West if I have to "Create a small (100m) first primary partition for grub" according to this suggestions (https://unix.stackexchange.com/ques...g-android-x86-only-tgrub-showing-when-booting), or, in alternative, modify the Debian 9.0.1 (on M2) "my 40_Costum" file to obtain a menu entry for Android in Debian GRUB. However I prefer a separate GRUB installed in the same physical memory unit where is installed the OS. I have to add that in Udoox86 Ultra internal EMMC 32GB I have this hardware device: mmcblk0boot0 and mmcblk0boot1 and mmcblk0rpmb root@amatronico:/home/stecolumna# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 477G 0 disk ├─sda1 8:1 0 469G 0 part / ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 7,9G 0 part [SWAP] sdb 8:16 1 7,5G 0 disk ├─sdb1 8:17 1 801M 0 part └─sdb2 8:18 1 3M 0 part mmcblk0 179:0 0 29,1G 0 disk └─mmcblk0p1 179:1 0 29,1G 0 part mmcblk0boot0 179:256 0 4M 1 disk mmcblk0boot1 179:512 0 4M 1 disk mmcblk0rpmb 179:768 0 4M 0 disk mmcblk1 179:1024 0 59,5G 0 disk ├─mmcblk1p1 179:1025 0 51,2G 0 part ├─mmcblk1p2 179:1026 0 1K 0 part └─mmcblk1p5 179:1029 0 8,3G 0 part Thanks to all
This is where I feel the problem might be for now. I think Android-x86 kernels don't have the needed commits to boot properly from the emmc, but I am looking into that part currently. The latest builds we have on the bliss downloads site for the udoo do have all the needed EFS bits to install and boot properly from the SSD though, so that is where I have my test builds installing to.
Dear Jon West I thank your for your answer and I want only add that after the installation of bliss_android_x86_64 I have also tried the "lunch Android" option and effectively it started the OS logo but in a loop, i.e. always and only the logo.
Not too sure you installed it using the latest .img from our website. Or if you installed the one the Udoo devs built. Either way, the first boot will show the bootanimation for a good 10 minutes potentially.
I have used android-x86_64-6.0-r3.iso [correction =] Bliss-v7.2-android_x86_64-UNOFFICIAL-20170615-1518.iso Thanks again
Dear Jon West Thanks to your observation about the fact that the logo can stay up to 10 minutes I have reinstalled and I launched Android before to exit and waited and finally the system started on. Android recognized two monitors and saw the available wifi networks. So it seems to recognize the wifi usb dongle. The problems are 1) that UI system blocked but I used ALT+F1 to obtain the shell and I used the command reboot 2) the reboot failed to launch the SO perhaps for the GRUB problem discussed in the precedent posts Now I will do more tests. Thank you
