Android x86 wifi driver

Содержание

no network in Android x86 on VirtualBox 4.1.2
Saved searches
Use saved searches to filter your results more quickly
Finnally add Broadcom Wifi drivers to package #4
Finnally add Broadcom Wifi drivers to package #4
Comments
Installation of WIFI Drivers in Base Android x86
Chih-Wei Huang
Ameya Soman
Chih-Wei Huang
WiFi & Bluetooth (RTL8723de) not working & other issues
crw
michel Alexa
Why can’t Wi-Fi be enabled in Android-x86 inside VirtualBox?
3 Answers 3

no network in Android x86 on VirtualBox 4.1.2

on virtualbox set the network interface to bridged (PCnet Fast III) and that’s all.

I added the above to /etc/init.sh and it didn’t work. Then I changed the network adapter to (bridged) PCnet-FAST III (Am79C973) rebooted and BINGO! I also needed to add «setprop net.dns1 8.8.8.8» to the init.sh file for the DNS (e.g. ping google.com) to work

Using this android-x86-4.0-RC2-eeepc.iso I only needed to add setprop net.dsn1 8.8.8.8 to the init.sh, reboot and it worked. Btw, using vbox bridge.

Thanks, also confirming that you only need setprop net.dsn1 8.8.8.8 in init.sh, after the interface is set to bridged. Works like a charm. It still says no internet connection, but the browser works fine.

@usman Write only «su» + Intro. After that, you are logged in as administrator, and you can directly write «vi /etc/init.sh».

Update: If Android x86 does not work well for you, you might want to look at AndroVM. I run it in VirtualBox and have had no hardware related issues.

Real Answer:

Somewhat of a follow-up answer since I can’t add comments yet. I think getting this setup is highly dependent on your host hardware. I am not using hardware that perfectly fits any of the current ISOs. So I tested all of them with all Ethernet settings to see what would work.

On a Dell Latitude D820 here is what I got:

eeepc — Bridged Adapter with PCnet-PCI II
tegav2 — NAT adapter with PCnet-PCI III
amd_brazos — No CPU support
asus_laptop — No eth0 option for any Ethernet adapter setting
s104t — Would not boot

For the two ISOs that would work for me (eeepc and tegav2), I added the following two lines to /etc/init.sh (as per the other answer)

netcfg eth0 dhcp setprop net.dns1 8.8.8.8

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finnally add Broadcom Wifi drivers to package #4

Comments

Lots of people have broadcom wifi adapters, its shame that its not working out of box.

The text was updated successfully, but these errors were encountered:

I have bcm4352. Wifi is actually loaded and can scan for hotspots from terminal. But it shows no hotspot in wifi setting, no way to connect?

Hello, having the same issue here, installed into a Dell Latitude E6410 with Broadcom wifi board. If there is any way to install wifi drivers please share. Otherwise system looks great.

Same issue on Toshiba nb205

Hello. I have USB dongle type WiFi (TP-LINK TL-WN725 Nano) which uses the RTL8188 chipset. Android x86 is not detecting it. How to install drivers?

Lots of people have broadcom wifi adapters, its shame that its not working out of box.

I don’t have wifi, how can I install the drivers?

Hello, having the same issue here, installed into a Dell Latitude E6410 with Broadcom wifi board. If there is any way to install wifi drivers please share. Otherwise system looks great.

ChiWei Hwang said Oreo K49 (kernek 4.9) work, but actually it didn’t work,
Rollback to Nougat R2 and it works 100%

Same here, on a Dell Mini 9 sporting Broadcom BCM4312. The OS works great, including LAN, but not WLAN and BT.

These instructions worked with mid 2012 macbook pro 13″ (non retina) booting android x86 8.1 r5:
«Just add EXTMOD=b43 to the kernel boot loading options.»

You need to mount the EFI partition (google that yourself) then navigate to /EFI/boot/android.cfg and edit add «EXTMOD=b43» to the menuentry on the kernel line after any of the existing parameters.

Источник

Installation of WIFI Drivers in Base Android x86

Возможно, адреса электронной почты являются анонимными для этой группы или вам требуется разрешение на просмотр адресов электронной почты ее участников, чтобы увидеть исходное сообщение.

I have installed Android Oreo x86 on my laptop HDD. I dual boot between Android and Windows. But in the Android System, I am unable to connect with my WIFI network and it seems that the system does not have any drivers. But when I boot Android x86 in debugging mode from the image in the Flash Drive, I can connect to my network. How can I get the drivers in the HDD ROM?

Chih-Wei Huang

Did you mean the WIFI works in debug mode
but not in the normal mode? If yes,
it’s the first time I heard that.

The driver loading methods are a little different
between debug mode and normal mode.
You may try to add AUTO_LOAD=old
to cmdline to see if it makes any difference.

Ameya Soman

I noticed that WIFI drivers work well in debug mode live USB ROM in one of my laptop. Due to storage constraints, I can’t see if it works with the HDD installed ROM as well.

On the other hand, WIFI drivers are never loaded in my second laptop which has features such as touch, two in one tablet pc. Drivers don’t load in either debug mode and live mode. I have also installed the ROM on my HDD. But the drivers are still not installed.

Chih-Wei Huang

2018-07-24 2:59 GMT+08:00 Ameya Soman :
> Basically I have two PCs
>
> I noticed that WIFI drivers work well in debug mode live USB ROM in one of
> my laptop. Due to storage constraints, I can’t see if it works with the HDD
> installed ROM as well.
>
> On the other hand, WIFI drivers are never loaded in my second laptop which
> has features such as touch, two in one tablet pc. Drivers don’t load in
> either debug mode and live mode. I have also installed the ROM on my HDD.
> But the drivers are still not installed.

Obviously the two PCs have different WIFI cards and
the second doesn’t have a driver in android-x86 image.

Check the WIFI card info (vendor, pci/usb id, etc)
and try to google if it has a linux driver.

Источник

WiFi & Bluetooth (RTL8723de) not working & other issues

On HP laptop, WiFi & Bluetooth not working on android-x86_64-9.0-r2 though working on latest Ubuntu, Manjaro linux. It has Realtek RTL8723DE adapter.

crw

michel Alexa

Regarding the issue with Bluetooth, I work with an RTL8822CU adapter with AOSP 10, and it’s not working on my side as well.

I suggest to try to commect via the Terminal with the following commands: << hciconfig >> ( will see on which interface the Bluetooth adapter is connected), << hciconfig interface up >> ( where interface is the BT interface on which the adapter is connected), << hcitool scan >> (to see what are the devices ready to connect), << hcitool cc BTaddr >> ( to connect to the device which have the Bluetooth address) and << hcitool auth BTaddr >> (to authenticate to the connection). Also, you can harvest the logs via adb command or dmesg and using grep option (for Linux)

Moreover, In my findings, after I configured the drivers (somehow) and it built successfully, I discovered that when I unplug the adapter (it’s and USB adapter) the Bluethooth app crashes form 15 to 15 seconds. So, I’m thinking that it’s a problem there as well.

Regarding the Taskbar app launcher, I recommend to use Quickstep. Or you can install another Launcher from F-droid marketplace.

Regarding the Screenshots, try using the Vulkan mode option in the GRUB menu. I discovered this workaround somewhere on this forum/group of discussions.

Please, if you find something please post here, since I am very interested about this topic (the BT).

Источник

Why can’t Wi-Fi be enabled in Android-x86 inside VirtualBox?

If I enter the Wi-Fi settings of Android-x86 (currently v8.1-r1) inside VirtualBox (currently v6.0.4) and turn it on, why does it just immediately get turned off? Some Android apps try to find devices inside the network so it’s essential (e.g. if you want to use Chromecast and iRobot Home).

3 Answers 3

Turns out according to the official docs, «VirtualBox provides up to eight virtual PCI Ethernet cards», which means no Wi-Fi card is available to emulate. Even if the host provides Internet to the guest via Wi-Fi, all the guest sees is Ethernet.

But if VirtualBox is incapable of it, then how does Genymotion bypass it?

Major update: thanks for using this very question as motivation, as of version 8.1-r2, Android-x86 simulates WiFi on its own!

so it’s still only a simulation? is there no way to use the WiFi adapter on the host (and, say, enumerate SSIDs and connect to wireless devices)?

It’s a simulation because the question was about a simulation. Due to the new feature, nothing stops you from using WiFi in the host, simulated as a wired cable in VirtualBox, then simulated as WiFi via Android-x86 itself. I confirm I’ve used this scenario to connect to wireless devices in the network!

If you’re running Android within a VM, I suspect the VM software is not allowing the Android VM to interact with your WiFi hardware directly, meaning that Android does not actually see that there is any hardware available for accessing WiFi. If you check your internet connection on the Android VM, does it show you’re connected to the internet via ethernet?

There may be a way in VirtualBox’s settings to give the VM direct access to your WiFi chip, but I highly doubt that would work based on the nature of running Android via a VM on desktop or laptop hardware.

Where can I check what you asked? Also, according to online searches, it seems even if you give direct access to Wi-Fi, the VM will still see it as Ethernet.

It would be in the VirtualBox settings somewhere (I don’t use VB, so I’m not sure where exactly). Like you said, though, I’m pretty sure it will only bridge the PC’s wifi connection so that Android sees it is a hard line connection (ethernet).

Just install it on Virtual Box software. After you install Android on VirtualBox, go to Setting and change the network setting just like this:

File — Host Network Manager
Choose the Adapter
- Attached to: Bridged Adapter
- Name: (select physical adapter)
- Advanced:
  - Adapter Type: Paravirtualized network adapter (virtio-net)
  - Promiscuous Mode: Deny
  - MAC Address: (insert MAC address, or leave default)
  - Cable Connected: V
Press OK and wait while Virtualbox is creating a host-only network interface

That’s still only a simulation. I think what people want here is to use the Wifi adapter on the host to, literally, connect to wireless devices as if you’re using a physical android phone. (enumerate REAL devices, see SSIDs, etc)

Источник