android-x86

How to install libhoudini on a custom Android x86 rig

久未见 提交于 2019-12-03 07:04:36
I'm currently making a custom built Android Marshmallow x86 64 on a mini PC. I've successfully installed the Android and now I'm trying to install libhoudini on the rig so that it can play ARM apps and games (porting the apps to x86 is not possible since they are 3rd party apps). How do I install and use it? When I go to its Github repo, it only has links with .sfs files in it. And also there is no documentation or tutorial whatsoever about how to install and use it. Thanks. So I've actually managed to find a pretty new tutorial about this and I've successfully installed and used libhoudini on

adb unable to connect to Android-x86 in VirtualBox today

有些话、适合烂在心里 提交于 2019-12-03 05:59:09
问题 I WAS successfully installed Android-x86-v3.2-eeepc in VirtualBox for a while. And it is a good method to help me to debug USB host applications on Android. The installation of such configuration is: Install VirtualBox Install Android-x86-v3.2-eeepc image into virtual HDD in VBOX Set network as "host-only" Enter console, type "dhcpcd eth0" to get IP address, like "192.168.56.101" Go to console of host, type "adb connect 192.168.56.101" Normally, it should be all right to get connected to adb

no network in Android x86 on VirtualBox 4.1.2

*爱你&永不变心* 提交于 2019-12-03 03:21:45
问题 My issue is nearly identical to this question. I tried those solution and none worked. But I am using a different Android x86 image. I'm using the ICS (4.0-RC1) asus_laptop image. (I tried a different image previously and couldn't get it to install.) I installed VirtualBox 4.1.12 on Kubuntu 12.04. I followed these steps and installed the android-x86-4.0-RC1-asus_laptop.iso image in my VM. It boots up and works correctly except for networking. Alt-F1 netcfg shows no interfaces up except the lo

adb unable to connect to Android-x86 in VirtualBox today

前提是你 提交于 2019-12-02 20:59:04
I WAS successfully installed Android-x86-v3.2-eeepc in VirtualBox for a while. And it is a good method to help me to debug USB host applications on Android. The installation of such configuration is: Install VirtualBox Install Android-x86-v3.2-eeepc image into virtual HDD in VBOX Set network as "host-only" Enter console, type "dhcpcd eth0" to get IP address, like "192.168.56.101" Go to console of host, type "adb connect 192.168.56.101" Normally, it should be all right to get connected to adb daemon running in Android-in-VBox. Today, it suddenly prompts me as following: C:\>adb connect 192.168

no network in Android x86 on VirtualBox 4.1.2

↘锁芯ラ 提交于 2019-12-02 15:32:53
My issue is nearly identical to this question . I tried those solution and none worked. But I am using a different Android x86 image. I'm using the ICS (4.0-RC1) asus_laptop image. (I tried a different image previously and couldn't get it to install.) I installed VirtualBox 4.1.12 on Kubuntu 12.04. I followed these steps and installed the android-x86-4.0-RC1-asus_laptop.iso image in my VM. It boots up and works correctly except for networking. Alt-F1 netcfg shows no interfaces up except the lo (127.0.0.1). eth0, which should be available, is not shown. That prevents me from trying the solution

dalvik.system.PathClassLoader can't find jni on Intel devices

断了今生、忘了曾经 提交于 2019-12-01 11:30:20
I'm having an issue where the dalvik.system.PathClassLoader can't find my jni file on Intel devices. I think it has to do with the structure of an aar dependency I have because once I removed that dependency, the jni file is found without issue. My aar dependency has x86 and arm libraries and my project only has arm libraries. The folder structure is: My Project src jniLibs armeabi libLibraryA.so My AAR dependency Project has: src jniLibs armeabi libLibraryB.so x86 libLibraryB.so With that structure, libLibraryA.so will not be found on x86 devices. I'm not sure if this is a gradle packaging

Cross Compile - tcpdump for x86

大城市里の小女人 提交于 2019-12-01 02:35:54
I need tcpdump binary for android-x86 . Here is what I have done: sudo apt-get install gcc-i686-linux-android sudo apt-get install byacc sudo apt-get install flex wget http://www.tcpdump.org/release/tcpdump-4.9.0.tar.gz wget http://www.tcpdump.org/release/libpcap-1.8.1.tar.gz tar zxvf tcpdump-4.9.0.tar.gz tar zxvf libpcap-1.8.1.tar.gz cd libpcap-1.8.1 export CC=gcc ./configure --host=i686-pc-linux-gnu --with-pcap=linux make cd .. cd tcpdump-4.9.0 export ac_cv_linux_vers=3 export CFLAGS=-static export CPPFLAGS=-static export LDFLAGS=-static ./configure --host=i686-pc-linux-gnu --disable-ipv6

Cross Compile - tcpdump for x86

旧街凉风 提交于 2019-11-30 23:05:26
问题 I need tcpdump binary for android-x86 . Here is what I have done: sudo apt-get install gcc-i686-linux-android sudo apt-get install byacc sudo apt-get install flex wget http://www.tcpdump.org/release/tcpdump-4.9.0.tar.gz wget http://www.tcpdump.org/release/libpcap-1.8.1.tar.gz tar zxvf tcpdump-4.9.0.tar.gz tar zxvf libpcap-1.8.1.tar.gz cd libpcap-1.8.1 export CC=gcc ./configure --host=i686-pc-linux-gnu --with-pcap=linux make cd .. cd tcpdump-4.9.0 export ac_cv_linux_vers=3 export CFLAGS=

No Audio in Android-x86

半腔热情 提交于 2019-11-30 14:11:28
问题 I've setup an Android-x86 image (4.0-RC1-eeepc) in VirtualBox on a Dell Latitude D820. This particular ISO is not for the laptop, but of all available ISOs it works the best. I have worked through some of the troubles I have come across (by not having an ISO for my device), but I haven't been able to get the sound working. The Android-x86 VirtualBox tutorial and other online resources directed me to use the ALSA driver with SoundBlaster 16, but this has not worked. This question got me to

Android resource for a specific product

感情迁移 提交于 2019-11-30 08:53:28
i got this code from Settings app... <string name="about_settings" product="tablet">About tablet</string> <string name="about_settings" product="default">About phone</string> then my questions are: from where at runtime the system load the correct string resource ? What must I do to add a new product? e.g. <string name="about_settings" product="laptop">About laptop</string> nandeesh from where at runtime the system load the correct string resource ? The system does not load this at runtime. The correct string resource is preloaded according to PRODUCT_CHARACTERISTICS defined for a specific