I am hoping a developer can get back to me on this or someone willing to help.
I downloaded the android source code and successfully compiled (no editing to code was made yet) i compiled as emulator eng (full-eng) but when i try to run the emulator command
$ emulator
i get emulator: ERROR: No initial system image for this configuration!
I put verbose on to see what happening and here is the log
[email protected]:~/WORKING_DIRECTORY$ emulator -verbose
emulator: found Android build root: /home/user/WORKING_DIRECTORY
emulator: found Android build out: /home/user/WORKING_DIRECTORY/out/target/product/generic
emulator: Found target ABI=armeabi-v7a, architecture=arm
emulator: Found target API level: 15
emulator: using core hw config path: /home/user/WORKING_DIRECTORY/out/target/product/generic/hardware-qemu.ini
emulator: found skin-specific hardware.ini: /home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/hardware.ini
emulator: autoconfig: -skin HVGA
emulator: autoconfig: -skindir /home/user/WORKING_DIRECTORY/development/tools/emulator/skins
emulator: found skin-specific hardware.ini: /home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/hardware.ini
emulator: keyset loaded from: /home/user/.android/default.keyset
emulator: trying to load skin file '/home/user/WORKING_DIRECTORY/development/tools/emulator/skins/HVGA/layout'
emulator: skin network speed: 'full'
emulator: skin network delay: 'none'
emulator: Found target ABI=armeabi-v7a
emulator: autoconfig: -kernel /home/user/WORKING_DIRECTORY/prebuilts/qemu-kernel/arm/kernel-qemu-armv7
emulator: autoconfig: -ramdisk /home/user/WORKING_DIRECTORY/out/target/product/generic/ramdisk.img
emulator: autoconfig: -sysdir /home/user/WORKING_DIRECTORY/out/target/product/generic
emulator: ERROR: No initial system image for this configuration!
can someone tell me how to fix it, and why im getting this error?
What device are you trying to emulate?
Im trying to emulate a galaxy nexus before i can practice on my g2x, so i simple downloaded the code from git and build the code and trying to run emulator command
Do you have a nexus image? I'm only guessing, but maybe you're missing the ROM/right root directory?
Sorry i'm afraid i still dont understand, these images here are used to recover a phone to stock upon flashing custom rom, and can be used with emulator along source code , the only pre built image was supposed to be the kernel, arn't all other images suppose to come by compiling the code? Do you mind elaborating on what i need to get emulator working with compiled source according to source.android.com i was just supposed to type emulator
Well which ROM are you trying to emulate?
Do you have a ROM you're trying to use?
Related
I am a new to using Linux, I just downloaded the SDK 1.5 and I am having some trouble getting the tools to work properly. For example. If I try to open the emulator it will just sit there and do nothing. I cannot get adb to work either. I set it up / the instructions. Any ideas on what I am missing? Thanks
easiest way to fix the adb problem is to move your adb command that is included in the SDK into your /usr/bin or /bin directory. if you have a problem with either of those then type cd ~/<sdk>/tools followed by ./adb the "./" tells the phone to run the command in the current directory, otherwise you could just type the directory to adb to run it i.e. ~/SDK/tools/adb that's all you need. as far as the emulator i have no idea because i have never gotten it up and running properly
How do I add the ADB command to usr/bin?
You can do as followed:
- Run the Terminal
- cd to your sdk/tools directory
- Run these command:
Code:
#./adb kill-server
#./adb devices
If you see your HTC has been remounted, it's done!
sudo mv ~/sdk/tools/adb /usr/bin/adb
tubaking182 said:
sudo mv ~/sdk/tools/adb /usr/bin/adb
Click to expand...
Click to collapse
Got it thanks for your help! I still can't get the emulator to work. Oh well Thanks again
What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
You created the AVD, right?
What do you get when you type:
Code:
android list avd
stovenator said:
What version of Linux? Are you using 64 Bit? What is the result of typing
Code:
java -version
Ubuntu version 9.04 & 64 Bit
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) Client VM (build 11.3-b02, mixed mode, sharing)
You created the AVD, right?
What do you get when you type:
Code:
android list avd
Click to expand...
Click to collapse
bash: android: command not found
They made a change in 1.5 SDK that you must specifiy the virtual device you want the emulator to run. if you just double click on "emulator", it will print the error to console and exit.
So first cd to the tools directory of the sdk and type android[return]
you will be given the commands that android (the program) will accept. you can also do this for emulator.
Great!! Everything is working well now. Thanks for everyones help!!
How Do I get fastboot working in Ubuntu?
jordanjf86 said:
How Do I get fastboot working in Ubuntu?
Click to expand...
Click to collapse
http://andblogs.net/fastboot/
fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.
billc.cn said:
fastboot is included in the 1.5 sdk, once you get adb working it should start working as well.
Click to expand...
Click to collapse
Actually it doesn't seem to be in the Linux 1.5 SDK; I had to build it. It's in the Windows SDK, though. Kinda weird.
Android SDK 1.5 emulator trouble in windows
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).
karan09 said:
hi i m new to xda and to android i m not tech savy
i install sdk 1.5 i try ddms it works good what when i try to lanch emulator nothing happnes and i try by going in command promt im getting this error can any one help me out in this
C:\Documents and Settings\jass>emulator
emulator: ERROR: You did not provide the name of an Android Virtual Device
with the '-avd <name>' option. Read -help-avd for more information.
If you *really* want to *NOT* run an AVD, consider using '-data <file>'
to specify a data partition image file (I hope you know what you're doing).
Click to expand...
Click to collapse
First, this is the wrong thread for such a question. This thread is about SDK issues in Linux, and you're asking about using debugging tools in Windows.
Second, if you say yourself that you are "not tech savvy", then I'm not quite sure why you are wanting to play with the SDK tools. I don't mean this in a derogatory way; I'm just not sure what it is that you're trying to accomplish.
That said, Android dev docs can be found here, and information specifically about the emulator is here.
- Chris
i want to alias ls='ls --color=always'. is there something like a .bashrc file for busybox sh?
bilclintonsdaman said:
i want to alias ls='ls --color=always'. is there something like a .bashrc file for busybox sh?
Click to expand...
Click to collapse
Just had a look at the busybox source and it says it uses the contents of environment variable ENV as a startup script so you could do
Code:
ENV=/system/sd/.bashrc ash
and it'll read /system/sd/.bashrc for your startup commands. Altrernatively, if you invoke it as a login shell (ash -l), it'll source /etc/profile then .profile from the current directory so if you create /system/sd/.profile to contain alias ls='ls --color=always' then as long as you do this
Code:
cd /system/sd
ash -l
you'll have your alias (I just tried this with JF1.51 and it worked great).
I also saw that it will record command history to the file named in HISTFILE so you may want to make your startup script look like this
Code:
alias ls='ls --color=always'
HISTFILE=/system/sd/.histfile
Also, keep in mind that this isn't bash -- you need to use ash shell scripting semantics.
Sweet! Thanks so much
~/.PROFILE
if you edit (may need to create it first) the .profile file in your home directory you shouldn't have an issue
i have the following in my ~/.profile file:
Code:
alias dir='ls -Alp'
alias cls='clear'
The next time you log in, you'll have your alias's
pre-compiled gnu bash
I can't remember where I found it, however, if you know enough to set it up, I have a pre-compiled gnu bash 3.2 file that allows you to execute something like this:
su -c '/path/to/bash --rcfile /path/to/.bashrc'
in the terminal emulator and you'll execute a bash shell with the .bashrc
I attached the pre-compiled gnu bash 3.2 in a zip file on the post, good luck getting it running! google is your friend!
I also compiled bash 4.0 for myself to use, but its kind of buggy since it was actually one of the first binaries that i've ever compiled on linux but it works! its just really slow >.>
I followed this tutorial to compile it
http://www.kbrandt.com/category/bash
I have downloaded the sources for the goldfish kernel and built it after which I cd into my downloaded AOSP directory and ran build/envsetup.sh and lunch selecting full-eng as my option. At this stage, $ANDROID_PRODUCT_OUT seems to be correct. I then ran "emulator -kernel ~/android-kernel/goldfish/arch/arm/boot/zImage -show-kernel -verbose @CustomAndroid-4.0.3-L15" within the same directory and it ran until this point where it hangs indefinitely:
emulator: autoconfig: -scale 0.737705
serial0 console
emulator: Could not open file: (null)/system/build.prop: No such file or directory
emulator: control console listening on port 5554, ADB on port 5555
emulator: can't connect to ADB server: Connection refused
emulator: ping program: /home/kubuntu/android-sdks/tools/ddms
emulator: ping command: /home/kubuntu/android-sdks/tools/ddms ping emulator 20.0.1.0 "" "" ""
Uncompressing Linux.................................................................................................. done, booting the kernel.
Click to expand...
Click to collapse
Any ideas what went wrong?
Ok I realized that I was building a 2.6 kernel for ICS which needs a 3.0 kernel but when I download either the 3.0 kernel or 3.4 kernel, there isn't a goldfish_defconfig, does anyone know how do I build the kernel for use with the emulator?
anonymous_coward said:
Ok I realized that I was building a 2.6 kernel for ICS which needs a 3.0 kernel but when I download either the 3.0 kernel or 3.4 kernel, there isn't a goldfish_defconfig, does anyone know how do I build the kernel for use with the emulator?
Click to expand...
Click to collapse
wow, i'm stuck here mate. To be honest i would suggest going back to a rom that you could install and run, without a problem.
Almost all terminal emulators let you to define an initial command, which will be run when you launch terminal emulator. But if you start a new cession in the emulator, say running cmd "su", the new session is not initialized as described in your initial command.
If your device is rooted and running latest Android OS, there is a way to make terminal emulator apps run your initial command for every session. Search directory /system/etc for file mkshrc, which is the initial command scrip for all terminal emulator and for all shell session in Android. You can put your initial commands there. Specifically, you can make it happen by doing the following:
. copy mkshrc from /system/etc to , say, /sdcard
. edit /sdcard/mkshrc and add in your own initial cmd
. remount /system/etc RW
. replace /system/etc/mkshrc with new mkshrc
. remount /system/etc RO
In addition, you'd better to make a backup copy of the original mkshrc just in case.
Not sure whether mkshrc is in all android version. My device is TF101 with EOS4 JB4.2.2. If you cannot find /system/etc/mkshrc, there might be other shell rc file.
Hi all, here is a package of command line tools I've put together, here's the readme with a few of the tools listed.
Android Command Line Tools
This Is Working Prefectly On Samsung Galaxy S3 'GT-I9305'
Your Phone Should Be Rooted To Perform These Steps!!!
Installation:
1. Copy The android-tools.zip To Your SD Card (Internal Or External) And Extract It
You Should Now Have A Directory Called 'android-tools'.
2. Open A Terminal On Your Phone And Type The Following
su
mkdir /data/tmp
cat /sdcard/android-tools/busybox > /data/tmp/busybox
cat /sdcard/android-tools/busybox-installer > /data/tmp/busybox-installer
cat /sdcard/android-tools/pkgs.tar > /data/tmp/pkgs.tar
cat /sdcard/android-tools/install.sh > /data/tmp/install.sh
cd /data/tmp
chmod 755 *
./install.sh
3. In Android Terminal Emulator Preferences, Set The Shell Path to '/system/bin/bash'
And Leave The Initial Command Blank.
4. Quit Terminal Emulator And Restart.
OpenSSH: ssh-keygen Save To '/data/local/home/root/.ssh/id_rsa'.
'ssh' And 'scp' Binaries Will Look For Keys In '/data/local/home/root/.ssh/'
So You Dont Need The '-i' Option, 'ssh-copy-id' Gets It From There Too.
Arduino:
There Is A Build Environment To Build And Upload Arduino Sketches With A Script Called 'arduino' To Wrap It Up
Type 'arduino --help' In Terminal To See Its Options, It Uses The Arduino-1.0 Core Library And I have Tested
Every Board And Can Confirm It Builds For All Boards Including 'micro' And 'leonardo'. It Uses 'avrdude'
'avr-libc-1.6.7' 'gcc-avr-4.5.1', I Wrote A 'arduino.nanorc' File For Writing Sketches Which Has All The
Functions And Constants Of The Arduino Core Library With The Same Colours As In The IDE.
Other Tools:
Some Other Binaries I Have Added Or Modified Are 'tar' With All Options Enabled, 'iwconfig', 'grep egrep fgrep'
With Colour And PCRE Enabled, '7zip', 'ipctool', 'shc' For Compiling Shell Scripts, 'ssh-copy-id', 'sed' With All Options
Enabled, 'macchanger', 'bootimg_baseaddr' In bash/sh, Compiled GNU 'core-utils', 'ncurses-hexedit', 'nmap', 'ngrep', 'nano'
'strace', 'gcc', 'g++', 'unpack-bootimg' In bash, 'unrar' And 'vim'.
Backtrack 5 ARM Is Configured And Ready To Go, Just 'mkdir /sdcard/Chroot'
And Copy Your bt5.img File Into It And Type 'bootbt', Then Edit The Scripts
For VNC Server 'startvnc' And 'stopvnc' To Reflect Your Screen Size, These
Are In The pkgs.tar
Replacing '/system/etc/mkshrc' With The One Included In This Package Enables Bash As Default In ADB Shell
If The Bash Binary Is Found In '/system/bin/bash' Else The Default Shell Will Drop Back To mksh.
Nano Does Not Save Through ADB Shell Using ^O Or '^X Then y' Method, Works Fine In Terminal Emulator App On Device.
There are more tools than listed above, here's the link> https://www.dropbox.com/s/yjumfljy7e1yoyc/android-tools.zip
If you're on an custom ROM and can't use the terminal emulator when you restart terminal emulator, get /system/lib/libncurses.so from stock ROM and use adb to copy it into /system/lib on your current ROM, I will fix this tomorrow.
Sent from my GT-I9305 using xda app-developers app
Please post the right link... this one is malformed.
sciurius said:
Please post the right link... this one is malformed.
Click to expand...
Click to collapse
op just updated the link, package is now ready for download again!
thank you, andreotti09!!!
greetz,
sUsH