Testing Android Oreo RC1 on Asus Transformer Mini T102HA

[Norberto Feliberty Jr.]

Hello just wanted to report that I tested out the Android Oreo RC1 build that was just release and WiFi does not work in this build. Also there seems to be a serious bug that causes my tablet to restart once the screen goes to sleep or if I press the power button to put the screen to sleep. I am happy to report that auto rotate, setting brightness, and sound all work on this build which is great to see as this is the first build that I have tried that the sound works on. I thought the sound did not work because support for sound for my device was not included in the 4.9 kernel but that is not the case as I see this build is also using the 4.9 kernel. 

[Jason Chu]

I've recently getting interest to give this a try (again).

1)

I remember last time, that to get the tablet to boot off the USB, only way was to attach the keyboard, press ESC or F2 (I forgot which) on boot, then select the USB drive.

Is there a way to boot off USB if bootable USB is attached, and boot WIN10 otherwise without needing to use the keyboard?

ie, plug is android USB -> boots android, usb unplugged or regular usb plugged -> boots windows.

I don't want to touch the internal eMMC, plus after running some benchmark, I've actually gotten faster RW speeds off the USB lol.

2)

In your opinion (seeing that you've pretty much tested all the different variants of android x86 available), which one works the best?  From what I gather from your posts, currently the android-x86_64-8.1-rc1.iso is one with least bugs given the major flaw of no wifi.  My bare minimum is to be able to watch youtube, if that's not even possible, then there's no point for me to dive in again.

As much as I do love the T102HA, great specs, great hardware, the Win 10 tablet experience is just horrible.  The "it runs the full win10" appeal quickly faded for me after some practical use of it.

I'm almost considering selling it for a convertible/hybrid Chromebook.

Thanks.

[Robin Lesewick]

The android-x86_64-8.1-rc1.iso works the best for the 102HA so far. However the WiFi does not work at all. However if you don't mind using it as a desktop and use a USB ethernet dongle, you can have network. The current build doesn't seem to support the WiFi driver at all (Qualcomm Atheros QCA9377), unfortunately. 

I found the following information on the adapter and adding into the kernel, however this is unfamiliar to me on Android. Seems its broken in newer kernels.

http://boggs.xyz/blog/qca9377-linux

[Jason Chu]

Thanks, but since I do plan on booting the android off the usb, so unless I use a usb hub, I don't have another usb port to work with.  And using a hub would turn this into a Franken-tablet.

[ngam...@gmail.com]

As far as I am aware of, the only way to boot off of USB on the tablet is to press & hold down the ESC key while booting up then select the USB drive.

--
You received this message because you are subscribed to a topic in the Google Groups "Android-x86" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/android-x86/cD7wXe6fffI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Jason Chu]

Thanks for that info.  That's sad, slowly moving towards Kijiji now....

[Chih-Wei Huang]

2018-08-15 22:50 GMT+08:00 Jason Chu <jason...@gmail.com>:
> I've recently getting interest to give this a try (again).
> 1)
> I remember last time, that to get the tablet to boot off the USB, only way
> was to attach the keyboard, press ESC or F2 (I forgot which) on boot, then
> select the USB drive.
> Is there a way to boot off USB if bootable USB is attached, and boot WIN10
> otherwise without needing to use the keyboard?
> ie, plug is android USB -> boots android, usb unplugged or regular usb
> plugged -> boots windows.

That's possible. But it depends on your BIOS.
The BIOS of my some devices (but not all)
can do that.

Try to change boot order to 1. USB 2. Internal HD
and see if it works as expected.