gsudo may not be needed in the commands above, but I used it for good measure. It may be the same in Android X-86 as well. gsudo is what the sudo command is in BlissOS.This may be done manually as well, and this command might not be needed at all. Disables bluetooth setting through terminal.Tells the bluetooth receiver to turn “on” and start transmissions as needed.It is possible this could be done through the Android UI as well. Terminal call to enable bluetooth on the device.Change hci0 to the ID of your bluetooth receiver if different.Puts the bluetooth receiver into an “off” mode.Shows the status of any bluetooth devices.The command was sudo nvram bluetoothHostControllerSwitchBehavior=neverĪs to why this is needed, I don't know, but hopefully Bluetooth is more stable in future versions of Android X-86.Ĭommand Chain (w/Sleep delays): hciconfig & gsudo hciconfig hci0 down & sleep 10 & gsudo pm disable & sleep 10 & gsudo pm enable & sleep 10 & gsudo service call bluetooth_manager 6 & sleep 10 & gsudo hciconfig hci0 up I also had to force Mac to not auto-capture my bluetooth USB dongle, but to let VirtualBox take it over. You may be able to automate this process on boot following a process similar to Īlso note that I am on Mac and had to get a bluetooth USB adapter since MacOS does not allow you to use the built in bluetooth. This is what I have found to fix my specific issue after toying with different commands. I suspect that it is not the memory size but something else.I have had issues in Android X-86 and BlissOS. I've tried changing the assigned memory size in the settings of the virtual machine to 2GB and then to 4GB, but starting Android still gets stuck at the same place in both cases. I was wondering what the reason is and what I can do to solve the problem? Thanks. I guess Android getting stuck is not because of a shortage of RAM. When I boot up the Android VM, the screen shows some information about booting Android, but eventually is stuck with a blank screen with a cursor on the top left corner, and at the same time Lubuntu has slightly changed free RAM as below $ free -h Total used free shared buff/cache available On Lubuntu currently free shows this: $ free -h Once it's recognized by ubuntu, there will be a phone icon showing up on the desktop screen. (VirtualbBox app: Devices > USB > check the USB corresponding to my phone). Then make sure the USB phone is found from within the guest OS (ubuntu desktop 18.04 in VirtualBox 6.0). In particular, I have assigned 1GB RAM to Android. I just connect my android phone with USB to my host (Windows 10). I have installed Android 7.1 on VirtualBox 5.2 on Lubuntu 18.04 on Thinkpad T400 following this tutorial.
0 kommentar(er)
