I have installed Android Studio version 2.3.3 on Windows 7 64-bit Enterprise.
Using the AVD Manager, I created a new device.
Issue: When I start the Android Virtual Device, a screen flashes and disappears. Based on some suggestions online, I read that we need to modify the Graphics settings of the Virtual Device however I don't get the option to modify these settings.
Below are the settings of the Android Device I have created:
Nexus 5X (5.2 1080x1920 xxhdpi)
Nougat (Android 7.0 x86)
Emulated Performance (Graphics -> Automatic)
Device: Enable Device Frame (checked)
Camera: Front and Back (Emulated)
Network Speed: Full and Latency: None
RAM: 1536 MB
VM Heap: 256 MB
Internal Storage: 800 MB
Keyboard: Enable Keyboard Input.
And here is the output of the command: avdmanager.bat list avd
Available Android Virtual Devices:
Name: username
Device: Nexus 5X (Google)
Path: C:\Users\username\.android\avd\username.avd
Target: Google Play (Google Inc.)
Based on: Android 7.0 (Nougat) Tag/ABI: google_apis_playstore/x86
Skin: nexus_5x
Sdcard: C:\Users\username\.android\avd\username.avd\sdcard.img
Related
Hey guys,
This is my first time developing apps for a device, please don't be too callous.
Prior to the release of Android Studio I was having a crack at eclipse with the android SDK and attempting to utilise the AVD simulator rather than the actual Galaxy Nexus I have right beside me. My issue was in fact the same as to when I converted to Android Studio, a rather consistent error:
Code:
Waiting for device.
C:\Android\android-studio\sdk\tools\emulator.exe -avd GalaxyNexus -netspeed full -netdelay none
Device connected: emulator-5554
Device is online: emulator-5554
Target device: emulator-5554 (GalaxyNexus)
Uploading file
local path: C:\Ryan\Android\MyFirstApp\build\apk\MyFirstApp-debug-unaligned.apk
remote path: /data/local/tmp/com.example.myfirstapp
Adb Transfer Protocol Error.
No such file or directory
The AVD Simulator boots up, Android Labels displays then fails after a matter of seconds. i understand the issue is obviously not related to the IDE hence why both eclipse and Android Studio are doing the same thing.
I Created an AVD with the following Properties:
Code:
Name: GalaxyNexus
Device: Galaxy Nexus (4.65"...etc
Target: Android 4.2.2 - API Level 17
CPU/ABI: greyed out as "ARM..."etc
Keyboard enabled
Skin enabled
Front Camera None
Rear Camera None
Memory options
- Ram: 512
- VM Heap: 64
- Internal Storage: 8 GiB
- SD 128MiB
Emulation options both left unchecked
Greyed out button for "Override the extisting AVD with the same name"
The basic default hello world app actually runs fine on my galaxy nexus on 4.2.2.
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
ryanspacef said:
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
Click to expand...
Click to collapse
Go to SDK Manager and hit the Install button. Mine still had 5 missing packages, including the ARM ABI, which would also explain why the AVD didn't boot. Hope this helps.
ryanspacef said:
Hey guys,
This is my first time developing apps for a device, please don't be too callous.
Prior to the release of Android Studio I was having a crack at eclipse with the android SDK and attempting to utilise the AVD simulator rather than the actual Galaxy Nexus I have right beside me. My issue was in fact the same as to when I converted to Android Studio, a rather consistent error:
Code:
Waiting for device.
C:\Android\android-studio\sdk\tools\emulator.exe -avd GalaxyNexus -netspeed full -netdelay none
Device connected: emulator-5554
Device is online: emulator-5554
Target device: emulator-5554 (GalaxyNexus)
Uploading file
local path: C:\Ryan\Android\MyFirstApp\build\apk\MyFirstApp-debug-unaligned.apk
remote path: /data/local/tmp/com.example.myfirstapp
Adb Transfer Protocol Error.
No such file or directory
The AVD Simulator boots up, Android Labels displays then fails after a matter of seconds. i understand the issue is obviously not related to the IDE hence why both eclipse and Android Studio are doing the same thing.
I Created an AVD with the following Properties:
Code:
Name: GalaxyNexus
Device: Galaxy Nexus (4.65"...etc
Target: Android 4.2.2 - API Level 17
CPU/ABI: greyed out as "ARM..."etc
Keyboard enabled
Skin enabled
Front Camera None
Rear Camera None
Memory options
- Ram: 512
- VM Heap: 64
- Internal Storage: 8 GiB
- SD 128MiB
Emulation options both left unchecked
Greyed out button for "Override the extisting AVD with the same name"
The basic default hello world app actually runs fine on my galaxy nexus on 4.2.2.
Not sure of my issue, I would assume configuration, though couldn't be sure.
Thanks ahead.
Click to expand...
Click to collapse
Have you tried to push your apps apk manually using the adb push command? If that does not work its probably a driver issue. Also you may try changing the sdcard size to >200mb or removing it altogether and only using internal. I would also use a much smaller internal size unless your app needs it. My AVD has an internal of 256mb and no sdcard and runs fine. The AVDs are very picky and have strange issues sometimes.
I'm looking to create an AVD for the HTC One M8.
Code:
./android create avd -n HTC -t [Which ID do I use?] --abi [Which ABI do I use?]
From:
Code:
id: 1 or "android-19"
Name: Android 4.4.2
Type: Platform
API level: 19
Revision: 4
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a, default/x86
----------
id: 3 or "android-21"
Name: Android 5.0
Type: Platform
API level: 21
Revision: 1
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : android-tv/armeabi-v7a, android-tv/x86, default/armeabi-v7a, default/x86, default/x86_64
----------
id: 4 or "Google Inc.:Google APIs:19"
Name: Google APIs
Type: Add-On
Vendor: Google Inc.
Revision: 9
Description: Android + Google APIs
Based on Android 4.4.2 (API level 19)
Libraries:
* com.android.future.usb.accessory (usb.jar)
API for USB Accessories
* com.google.android.media.effects (effects.jar)
Collection of video effects
* com.google.android.maps (maps.jar)
API for Google Maps
Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in
Tag/ABIs : default/armeabi-v7a, google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64
Thank you in advance!!!
Also, how do I create a custom hardware profile?
When trying to do so, I get prompted with:
Code:
Name of the AVD being run:
avd.name [<build>]:
I input my build name and it just keeps asking.
Thoughts?
Hello all,
I have recevied an old tablet "goClever i102 ( Airis Kira N10020) and it is slow.
Here are it's specifications:
• 10" Wide TFT (1024x600)
• ARM11 up to 1 GHz Processor
• Memory 512 MB DDR2
• Storage Flash 4 GB
• WLAN - LAN 10/100
• mini HDMI - Web-Cam - 4x USB
• micro SD/SD-HC Card Reader
• Dimensions 246.6 x 172.7 x 24.5 mm.
• Weight ~ 0.90 Kg.
• Android 2.3 OS
The manufacturer's page for the device:
http://www.airissupport.com/SupportHome2.aspx?Codigo=N10020
Here are some aditional informations I gathered by openning it:
Processor
========
Infotmic imapx210bm1-80
pcc265 oop-1
1133
Stuff written on the main board
========================
pc1051
ver.1.2
2011/12/14
s-m
940-0
e305905
Some integraded circuits I could not identify
==================================
4x Samsung k4t1g164qf-bce7
Hynix Nand Flash Memory
====================
H27UBG8T2ATR-BC
PARALLEL 8M FLASH T
====================
MCXMX29LV800CBTI-70G
I rooted the device and I posted the instructions here:
http://forum.xda-developers.com/android/help/rooting-goclever-i102-n10020-t3119091
I would like to install on it Arch linux or some other linux core.
I set up a virtual machine with linux, installed a cross-compiler and the toolchain to build for ARMv6 processors and then I tried to build a bootloaded and a kernel for the tablet. It succesfuly built the kernel, just to test the toolchain ,but soon I realized that I could not configure u-boot for this specific processor. I could not find any pre-made configurations files for it. I don't have much knowledge about how to build a kernel or a bootloader.
Could anyone help me regarding this issue or give some instructions how to manually configure u-boot?
PS: I tried to boot on some RasberryPi softwares that I could find on the internet but it did not boot. Also I tried some linux software for the tablets Airis Kira N7000 / N8000 / N9000 that I found here: https://kirbian.wordpress.com/descargas/airis-kira-n7000-n8000-n9000/ ,and booted the kernel for a very short time(it displayed something like uzImage.bin and a loading bar), but then the screen went black with the cursor blinking on the left. After this it remains in this state, nothing loads or changes. After I reboot it, it loads the stock rom (Android 2.3.3)...
Thank you in advance!
Hi
I have tried usb key, hdd install using both 32 and 64 bit, however after the grub screen my display goes blank. I have waited over 30 mins but it does load and show remix screen. Here is my config. I have this running fine on my old HP pavilion and its great so would love to be able to run it on my large Acer. Any help appreciated
OS Name Microsoft Windows 7 Ultimate N
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name KITCHEN
System Manufacturer Acer
System Model Aspire Z5610
System Type x64-based PC
Processor Intel(R) Core(TM)2 Quad CPU Q8200 @ 2.33GHz, 2327 Mhz, 4 Core(s), 4 Logical Processor(s)
BIOS Version/Date Phoenix P01-B2, 19/01/2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 4.00 GB
Total Physical Memory 3.87 GB
Available Physical Memory 1.63 GB
Total Virtual Memory 7.74 GB
Available Virtual Memory 5.45 GB
Page File Space 3.87 GB
Page File C:\pagefile.sys
Name NVIDIA GeForce G210M
PNP Device ID PCI\VEN_10DE&DEV_0A74&SUBSYS_069110DE&REV_A2\4&357F6195&0&0008
Adapter Type GeForce G210M, NVIDIA compatible
Adapter Description NVIDIA GeForce G210M
Adapter RAM 512.00 MB (536,870,912 bytes)
Installed Drivers nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver Version 8.17.11.9666
INF File oem5.inf (Section013 section)
Color Planes Not Available
Color Table Entries 4294967296
Resolution 1920 x 1080 x 60 hertz
Bits/Pixel 32
Memory Address 0xFC000000-0xFCFFFFFF
Memory Address 0xE0000000-0xEFFFFFFF
Memory Address 0xDE000000-0xDFFFFFFF
I/O Port 0x00002000-0x0000207F
IRQ Channel IRQ 16
I/O Port 0x000003B0-0x000003BB
I/O Port 0x000003C0-0x000003DF
Memory Address 0xA0000-0xBFFFF
Driver c:\windows\system32\drivers\nvlddmkm.sys (8.17.11.9666, 13.09 MB (13,728,616 bytes), 17/02/2010 06:13)
A typical Windows OS ready x86_64 Android emulator is made of the 2 components Virtualbox - host - and Android image - client OS - so as with Bluestacks, MEmu, LDPlayer, etc.pp.
Actual x86_64 Virtualbox v6 - without extensions - occupies 228 MB, an x86_64 Android 11 GSI image occupies 1.5 GB disk space, so in total ~1.8 GB at minimum are used by an Android emulator based on Virtualbox, whereas
Microsoft's Windows Subsystem for Android ( WSA - it's Android 11 ) occupies 2.03 GB.
BTW: If you add Virtualbox Extension pack, then additional 10 MB diskspace is used.
Resume: An x86_64 Virtualbox based Android emulator suprisingly takes ~ 10% less disk space than WSA.
i prefer wsa because due its intel-arm-translator it can run apps compiled for arm, too