Hot answers tagged terminal
11
Android System Info is a free app from the market which will tell you more details about your phone than you ever wanted to know. It has all the details you want about your CPU and Memory and much much more.
Install it, start the app and check the System tab for all the information you are looking for.
7
Using adb, I believe it is possible:
am [start|instrument]
am start [-a <action>] [-d ] [-t <mime_type>]
[-c <category> [-c <category>] ...]
[-e <extra_key> <extra_value> [-e <extra_key> <extra_value> ...]
[-n <component>] [-D] [<uri>]
am instrument [-e <arg_name> ...
7
These free apps in the Market claim to be able to display your logcat, and don't make any mention of root. Should only take you a few minutes to try them out:
CatLog
aLogcat
LogViewer
5
Settings -> About Phone should tell you most of what you want to know. Failing that, it will at least tell you a model name which you can then search google for more info.
My 'About Phone' lists Model, CPU info (i.e. what CPU) and Memory info among other things. But I am running CM7 with Gingerbread.
5
Like Sachin Shekhar said, you must use the following command :
am start -a android.intent.action.MAIN -n <package_name>/<full_class_name>
See a concrete example :
getting the apk file from your Android device or any Market places
running this command :
aapt dump xmltree com.android.settings*.apk AndroidManifest.xml
I would like to start ...
4
You don't need to root your phone to run adb logcat with the Android SDK, but I did just test it in my Terminal Emulator and I did have to be root (used the su command -- my phone is already rooted) to run logcat in the terminal on my phone.
So yes: if you have root on your phone you can run logcat from a terminal on your phone.
4
You don't need root. You also don't need a terminal, for an app to use its own private utilities. But if you want vim, Terminal IDE provides that, a number of other utilities (git, ssh, tmux), the ability to use bash or Java as a 'scripting language' at the terminal, and the ability to create and install Android apps on-device. I use Terminal IDE and vim ...
4
You should be able to call the messaging intent with
am start -a android.intent.action.VIEW "sms:numberhere" -e "sms_body" "hello"
Using the intent command as described here:
http://learnandroid.blogspot.com/2008/01/run-android-application-from-command.html
http://stackoverflow.com/questions/4967448/send-sms-in-android
4
The following terminal command should enable Bluetooth via adb shell or Terminal Emulator app:
su
am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
On most versions of Android, this command will present a pop-up window to the user asking to confirm request to enable BT. I believe this was done for security purposes whenever an app that is not ...
4
The su binary works just like it does on Linux; it runs all commands that follow as root until you type exit (or terminate the process, etc.). sudo <command> essentially does:
su
<command>
exit
Android doesn't normally include sudo, so If you wish to launch commands like you would with sudo, the syntax is as follows:
su -c ...
4
Native binaries (as the mkfs.* tools are) need to be compiled for the platform they should run on. So if you take the mkfs.ext3 from your Ubuntu workstation, which probably is either x86 or x86-64, it will not work on your Android device, which most likely uses ARM architecure.
4
Use this:
am start -a android.intent.action.MAIN -n <package_name>/<full_class_name>
To control an app, you'll have to put correct values of <package_name> and <full_class_name> in the command. For example, you can use com.google.gmail/com.google.gmail.check_mail (Hypothetical names) as last part of command.
Obtaining package name ...
3
There are native programs available on Android for creating file systems, and in most cases they reside in a directory below /system (my Motorola Droid 2 e.g. has them in /system/xbin. Depending on the file system you want to create, you can chose between:
mkfs.ext2
mkfs.minix (unlikely you want that -- and it might even be not available with your ROM)
...
3
Use one of those:
cat /proc/mounts
mount
# free disk space of mounted fs'
df
# this shows you available devices
cat /proc/partitions
ps: Lines containing asec are moved-to-sdcard apps (it's each an encrypted volume per app for security reasons)
3
As eldarerathis already mentioned: On many (if not most) devices supporting an SD card, this card is mounted with the noexec option -- which means as the name suggests: "no exec from here", i.e. you cannot execute anything from the sdcard.
Again, one solution was already mentioned by eldarerathis: Try a different storage. You've got the power, your device ...
3
Most of the terminal commands in android are the limited version of standard Linux/Unix/POSIX terminal commands, provided by the toolbox program. Notably absent from toolbox is the cp (file copy) command, you must use cat file1 > file2 instead. If you spend a lot of time in the shell, you may want to install busybox, which provides a richer set of ...
3
BTEP has a "Using Better Terminal Emulator Pro" page on their wiki which explains most of the special shortcuts and keys. The basic breakdown of what you're looking for is:
For directional input: Either use a keyboard that supports this or use BTEP's virtual direction pad feature. You can access it by tapping the screen when the keyboard is visible, ...
2
Since I stumbled over the same problem as you did I started to compile a list of useful commands in the Android Shell including examples. A German version is on my blog.
2
I'd think a simple web search with the name of your device and "specs" should return all of the information you need. There are any number of sources of this information on the Web.
Here's a link I found after a simple search: http://chinagadgetdeals.info/official-rockchip-based-apad-irobot-android-tablet/
2
Note sure if this question should really been have migrated here. But this is a typical case of a vacuum that we have here. It's not really an android end-user question and on the other hand not a android programming question.
Anyway it looks like a typical codepage/localisation problem:
"<" on an US layout is ";" on an German (and maybe others) ...
2
This is a known design problem when using statically linked libresolv and glibc.
You have 2 options:
Use Google Android's native libc Bionic library instead of glibc.
Build busybox to search libraries in /system/lib (or make the necessary links e.g. /usr/lib -> /system/lib ). Place ld-linux.so.3, libc.so.6, libresolv.so.2, libnss_dns.so.2 in your ...
2
Emulator app should be able to run another app from its own directory. That directory is called something like /data/data/com.super.emulator. Try giving the full path to the app you want in emulator.
If you want to get a compiler for Android, you can use NDK. Easy to get, free to use.
Can't you also push your file to /system/bin via adb? I don't know if ...
2
As I wrote in my comment, there are some special characters needing extra care when working at the shell prompt (or in shell scripts). One of them is the $ sign, which usually indicates a variable. If that should be taken literally, you need to escape it (or enclose the entire string by single quotes). Similar rules for quotation marks.
How your command ...
1
Moved from comments and expanded.
Invoking the script with the shell directly sh .profile arg1 arg2 should work. If it become cumbersome to invoke the shell and typing the arguments, you can also create an alias, most terminal emulators allows you to specify an initial command to run at the start of a session.
1
You will probably be unable to directly execute scripts from your sdcard. At least without root. Reason is, with most ROMs sdcards are mounted using the noexec flag -- which means, as the term suggests: "no exec from here". Of course, having root you could simply remount the sdcard while removing this option.
Why might this option be forced? I'd say for ...
1
I'd personally recommend using a terminal emulator or adb shell and then using the ls command. You can get the UID's listed by name if you use the -l flag and listed by number with the -n flag. Note that in the /data directory you'll need root permission in order to index the files/directories, so ls will fail with a normal user:
root@android:/data # ls -l
...
1
Most likely you can't run the program because of libraries on the device you ripped it from being missing from the device you copied it to.
Since your end goal is to compile a program and run it natively on the phone, might I suggest you use the Android NDK? The NDK documentation includes STANDALONE-TOOLCHAIN.HTML which explains how to cross-compile a ...
1
The android terminal emulator uses busybox linux. Hence you should look at the busybox commands to find out what all you can do with it.
Follow this link
try this command
fdformat DEVICE eg. fdformat /dev/sdcard
1
This doesn't happen when you run ssh as root.
/sdcard is an unsafe(!) location for ssh client config and valuable keys (some users don't even encrypt their keys for reasons of laziness). Each app has read access to that location, so this is most probably set deliberately not to /sdcard/.ssh for security reasons.
If you have root access, create a symlink ...
1
Rooting your phone gives you root access (duh!), but that doesn't mean accessing a shell requires you to root your phone. You can use ADB to connect to your device and gain shell access.
You can also use ConnectBot to access your device's shell on the device itself.
This will give you normal access to your device and you will not be able to run su to gain ...
Only top voted, non community-wiki answers of a minimum length are eligible
