If your talking about the option "Enable Native Bridge" then yes I do have it enabled.
Heres the link to the apk I was using: https://www.apkmirror.com/apk/electronic-arts/plants-vs-zombies-free/plants-vs-zombies-free-2-5-00-release/plants-vs-zombies-free-2-5-00-android-apk-download/
I just want to play some classic PVZ but every time I install it and open it, it crashes immediately
I always say, start with the newest available, currently based on Android 9 and try it in live mode - this will run it off a flash drive - skip the Google account step, just connect to Internet and try the hardware - keyboard, touchpad, camera, display, etc. - if that doesn't work or doesn't boot (system requirements sometimes go up with every new release) then go one version down to 8, etc. As long as what you end up is relatively new - I could be mistaken but I believe KitKat (4.4) or newer is needed for Play Store access.
For the desktop-like experience, there are a few launchers that mimic a kind of desktop mouse/keyboard focused control. Some builds come with a home screen called Taskbar as an option, which if you look at the screenshots on the listing it's a lot more similar to the kind of thing you're talking about.
So just to make sure, you can check your Widevine level with the app DRM info - lower numbers are "better". If your existing box says you have some super high level or no level or whatever then services you're using probably don't care about Widevine.
Looks like the 5.8 kernel includes support for that device, remember Android runs on an old 4.19 kernel (even my Pixel 4a 5G running the latest Android 12 runs on the 4.19 kernel). Other dongles like the one from Panda (it's Bluetooth 4.0) should work out of the box on Android, and should passthrough with KVM - https://www.amazon.com/dp/B00BCU4TZE/ - this is the dongle I use in general on my PC for headphones and it was plug and play - it comes with a disk and I never even touched it - thing's as easy to use as a mouse.
I see. The Taskbar can be updated from the Play Store - I wonder if there's a specific bug you're experiencing that may have been fixed already, if not may be worth reporting. Here's a link to the Play Store version: https://play.google.com/store/apps/details?id=com.farmerbb.taskbar
Android-x86 comes with two home screens. One is the standard Android screen people are used to on phones and tablets, the other is a homescreen called Taskbar, which you can download from Google Play as well, here is the link: https://play.google.com/store/apps/details?id=com.farmerbb.taskbar - Taskbar is a lot more like a mouse and keyboard oriented PC-style interface, the standard Android home screen is usually optimized for touch.
Can you provide a link to the Bluetooth adapter you tried to get to work?
FYI my recommendation for Bluetooth adapters is this one from Panda Wireless: https://www.amazon.com/dp/B00BCU4TZE/ref=cm_sw_r_apan_glt_i_64ENNF2YJR9T444K2XVA
Well, if none of the suggested methods work, you could try out Zank Remote.
It doesn't require rooting, just that both the device to be controlled and a phone is on the same WiFi network.
It does its job by functioning as an Accessibility Service and displaying over apps, and that'll make it work as touch emulation service.
The GPlay link, and App Store link.
In both cases, your phone will be used as a pointing device.
Sure, so the idea with a media server is it's a computer that's permanently connected to the network - like with a static IP and with Ethernet ideally. And you can store music, and pictures, and movies on it, and then you can access them from any device on the network. An example of this is a Plex server, but I think Plex is a paid service if you want some of the really cool features.
For retrogaming, you can install the RetroPie software on top an existing GNU/Linux distribution, for example Lubuntu, that you can get to install on your machine, with directions here: https://retropie.org.uk/docs/Debian/#installation - You should be able to play like GameBoy, Super Nintendo, etc. Definitely not PlayStation 2. I just ran this on a little virtual machine with 1 GB of RAM and it took about 15 minutes, it might take longer on your setup with your processor.
As far as upgrading goes, I'm not sure how much 1 extra stick of 1 GB RAM is going to help, but it may be worth a try if that's something you're comfortable doing. I also notice you have an optical drive, if you are comfortable removing the optical drive, you can get an SSD in that slot instead with an adapter, that could increase boot speed.
That being said, lubuntu uses 464 MB of RAM at idle, normally that's very low, but it's almost half of your RAM, so if you can get a second stick I think it might help.
The company panda wireless makes Bluetooth and wifi dongles that work out of the box. Have a look at their product page for Amazon links. For example their Bluetooth adapter: https://www.amazon.com/dp/B00BCU4TZE/
use set orientation v1.1.4
https://apkpure.com/set-orientation/com.googlecode.eyesfree.setorientation
I have it both on Android x86 and Firestick.
Found the issue - https://hackmd.io/@StanS/Android-x86
Need to edit the startup code for it to work, as per link above
Obce installed, at boot menu
press e
press e
replace quiet to nomodeset xforcevesa
press enter
press b
as you see android system on, press Alt+F1
type in
mkdir /mnt/sda
mount /dev/block/sda1 /mnt/sda
vi /mnt/sda/grub/menu.lst
press i to edit, replace quiet to nomodeset xforcevesa
press Esc to return read-mode
press :w then press Enter
press :q then press Enter
type reboot then press Enter
Now switched over to a FireStick 4K Max
No. Drivers don't work like that - they come from the kernel and it needs to work out of the box.
See if you can disable automatic screen rotation. It's a common thing in touch laptops to have the panel mounted sideways or upside down and to then expect the OS to "fix" this.
You can try manually controlling the orientation with an app like orientation control.
You can find a current list of working Androidx86 OS ports HERE. These are much more light weight than Androidx86 downloaded from the official Androidx86 project site, however it is hit and miss with different Wifi adapters. You just have to google your make and model wifi adapter to find out if/how to use it with the OS your are using.
Not really dead, Android-x86 is just very very niche so not many people. The last stable release was less than a month ago.
Auto installing is exactly what you don't want to do. You just said you want to dual boot but this is not for dual booting.
>If you want to use Android-x86 as the only OS in your device, you may choose "Auto Installation" under the "Advanced options".
>
>https://www.android-x86.org/installhowto.html
To dual boot you will want to select the "Install Android-x86 to harddisk" option then in the "Create/modify partitions", partition your main Windows partition and then format the new empty partition to ext4 and install onto that, and select yes when it asks you install the GRUB which will let you select the partition to boot into when you turn on the computer.
That's what I am trying to test. If you look at the release note , there's an option to enable support for arm (from the release note): "Support arm arch apps via the native bridge mechanism. (Settings -> Android-x86 options, 64-bit only)".
I haven't got time to test properly yet. Whenever I turn that option on , it turns off automatically, I think that's some of glitch right there, have to wait for the next update I guess.
lolthere are no moderators here, moderators are dead since 2 years they havent come. you could have given gift card in secret after someone solved your problem instead of trying to get attention, even if you gave a gift card or not people help you
contact android x86 developers
Make sure you are using a 64-bit ISO, and verify it by comparing it's sha1sum value - an easy way to do this in Windows is go to the folder where your ISO is stored, hold CTRL+Shift and right click, and select Open Powershell here. Type the following command:
CertUtil -hashfile "android-x86_64-9.0-r2.iso" sha1
Replacing the file name with the filename of your ISO if it is different. It will then spit out a long piece of text, compare that to the piece of text under "sha1sum" on the download page. Both of those need to match exactly. If they do not you need to redownload your ISO.
You can also try going into your UEFI settings (probably F2) and see about disabling "Secure boot" (under the "Boot" tab) and "Load legacy option rom" also under the boot tab. You may or may not need to disable secure boot.
If that doesn't work make sure your UEFI firmware is up to date, if you got the machine brand new there may be an update that will make booting from USB work more reliably.
Not sure what happened to you there for a loop to happen but I think its best to try the other option "Upgrade" or re-install fresh to be on the safe side at this point.
Stick to instructions here: https://www.android-x86.org/installhowto.html
Hope all goes well for you bro!
----------------------------------------------------------------------------------------------------------------
Update: I just remembered there is a guide by the Android x86 Team here:
https://www.android-x86.org/installhowto.html
Scroll down until you see a section called "Auto-Update" OR the "UPGRADE" section.
I think the "UPGRADE" section is what you're looking for and the "AUTO-Update" might be more for Updating from eg. Android 9.0r1 to Android 9.0r2 (Then again I think both work to do the same thing ...whether it be to jump from release 1 to 2 or from android 8 to 9.)
Good luck bro !
https://www.android-x86.org/download.html
Download .ISO, open it and copy/extract the files to a formatted (fat32) usb (no need for Rufus), have laptop boot from usb and run the install to HDD. I used this same method with my dual boot setup for windows 10 + Android x86 on my Surface Pro 3. Thank me later
Use Microsoft's instructions to reinstall Windows 7 however Windows 7 is out of support and security updates have stopped a while ago. You can use your Windows 7 key to install Windows 10, just download the media creation tool from Microsoft - it will take care of formatting your flash drive, downloading and flashing the installer and verifying it.
The best way to see if it it will work is to just run it - download the Android-x86 iso file from https://www.android-x86.org/ and write it to a USB drive with Etcher from https://www.balena.io/etcher/ and boot it - there's an option called "live mode" which runs the whole OS off the flash drive. You can skip account creation as nothing is saved anyway, but connect to wifi, test to see if things like touch and mouse and sound and bluetooth and camera and battery indicator, etc. works. If it works in "live mode" it won't work worse installed to the hard drive.
If you have any issues either getting it to boot or with specific hardware peripherals or chips let me know and I'll see if I can't help troubleshoot.
Not exactly. Easiest way is with a program called Etcher - it writes the ISO to the flash drive but note it will delete everything else on the flash drive so keep a backup if needed. Then when you turn on your computer you need to hit a key to enter the boot menu which is different usually per manufacturer, sometimes it's F12, F2, ESC, etc. The boot menu will let you select your usb drive to boot from.
Alright well to run Android-x86 you download a .iso file from their website, write it to a flash drive with a program called Etcher and tell your computer to boot off the flash drive so you can rest Android. So which .iso file did you try to boot when you were having problems?
If you need to clear your USB installer, I would just use Etcher from https://www.balena.io/etcher/ - it's the easiest to use, it's three steps 1) select your iso/img file 2) select your flash drive 3) click start - there's no guess work or any settings you need to worry about otherwise with Etcher.
I'm not sure of that software, can you fully format and then try with Etcher? Also can you verify the sh1 sum of the file you downloaded matches the one on the download page?
Android-x86 shares a lot in common with typical desktop GNU/Linux distributions, but with the addition of Android specific patches and Android-x86-specific patches. The first step to troubleshooting Android-x86 hardware support is try booting desktop-grade GNU/Linux. Specifically, download Ubuntu and write it to flash drive using Etcher. If wifi works it means that support for your hardware was added to the Linux kernel in a version newer than what Android-x86 ships. Try it and report back.
Android-x86 shares a lot in common with desktop-grade GNU/Linux though it uses an old driver set. My advise is to download Ubuntu and write it to a flash drive with Etcher and boot it - if it works then you just need a newer kernel version which Android-x86 typically pushes with new updates. So that's where I'd start.
I don't know that nano is installed on Android - it's a GNU program and Android does not ship a lot of GNU stuff. Grab a text editor, there's plenty out there, for example here's one and see if you can use a file manager (with root) to access the file. That being said what you're asking for is akin to piracy.
Yeah, I'm a big fan of the Panda Wireless products - they make both Wifi and bluetooth dongles. Here's their Bluetooth dongle, it works out of the box - no disk or installation of any kind is needed (except maybe on Windows), just plug in and it works: https://www.amazon.com/dp/B00BCU4TZE/
Do you know the model number of the ethernet chip in your computer? Alternatively the make and model of the computer. The short answer if I had to guess I'd guess that particular card or chip is not supported or not yet supported, and an easy fix is a USB Ethernet adapter which costs around $12 to $13.
I believe I wanted the same setup as you (wanted to play pinball fullscreen with the monitor mounted in portrait orientation) and had no luck using a modern version of Android. I'm not in front of it right now, but I believe I had to use an older build like Oreo and then a rotation app like Rotation Control.
I would've rather used something newer but I could not get anything to work and the older build didn't affect me much.
Here is what I use. Simple and clean interface
​
https://play.google.com/store/apps/details?id=org.crape.rotationcontrol
In version 6 rotation rotated the screen, and https://play.google.com/store/apps/details?id=com.devasque.rotationlocker could force rotation regardless of what apps wanted. I used it to force landscape on my laptop, but you could force portrait.
In version 8.1 landscape uses the whole screen and portrait uses the centre part only, still upright. This is actually better on a laptop, because having the picture sideways when an app wants portrait is a problem, but not for your application.
If a device manufacturer has done everything correctly a driver should be preinstalled in the kernel and not require any effort from the user. TP-Link has not done their driver correctly to this standard, at least for this device. There is a driver on their website https://www.tp-link.com/us/support/download/archer-t2u/ but with an install guide for Ubuntu on the desktop, Raspberry Pi, and a few others, but not Android I'm afraid. I would say your adapter is not going to be compatible without intervention from TP-Link.
Essentially they're having you download and install the driver yourself but I'm not sure Android has all of the normal GNU/Linux commands and tools available.
Fwiw, I don't think the company is consistently bad. Years ago I picked up this PCI-E adapter from Amazon https://www.amazon.com/dp/B00A0VCHQE/ref=cm_sw_r_apa_i_nDmOEbRWVSR2B and to this day it works out of the box without any intervention on Ubuntu and Android.