Use at commands in android

Добрый день уважаемые форумчане и разработчики!
Мучаясь над решением одной задачи, общение с 3g модемом Android планшета с помощью АТ команд, решился к Вам обратиться за помощью.
Надеюсь выйдет интересная тема и кто-то из разработчиков возьмется за создания приложения, которое, я уверен на 100 %, можно будет коммерциализировать на Плей Маркете ). Планшеты с 3G модемами очень популярны и спрос растет непомерными шагами. Модемы производители устанавливают урезанными в функционале для экономии затрат.

Имея 3g планшет (с отключенной возможностью звонков, смс, проверки остатка на счету и пр. излишек полноценного радио) я с помощью терминала в режиме SU и АТ команд пытался в чем-то успешно, в чем то безуспешно:
1. Подключиться к диагностическому порту 3g модема (/dev/ttyUSB2) и послать стартовую команду АТ — успешно
2. Отслеживать лог радиомодуля logcat — b radio — успешно
3. Получить информацию о модеме ati0 — успешно
4. Отправлять USSD команды проверки баланса AT+CUSD=1,*111#,15 — безуспешно

Поэтому хочу начать дискуссию о возможности ат команд на Android что-бы:

1. Отправлять USSD запросы (команда CUSD) — и обработка их ответов (в т.ч. стандартные заготовки — счет, перевод, пополнение ваучером, и пр. реализовать шаблонами)
2. Отправки СМС (команда CMGS) — с возмоностью хранения отправленных
3. Получение (формально чтение с якейки сим карты) СМС (команда CMGL) — с памяти сим карты, и после прочтения чтобы удалялись с катры и сохранялись локально
4. Перевод модема в режим толко 2g\ только 3g\предпочтительно 2g\ предпочтительно 3g
5. Подключаться к интернету , в т.ч. через ручные APN точки
прочее по мере дальнейшего пользование что-то еще захочеться

Я на нетбуке имею 3ж модем и к нему вотчер, даю скриншот может поможет к.л.

Сообщение отредактировал B_B — 24.12.12, 22:58

Источник

Send AT Commands to BLE 4.0 Module From Android Phone

Introduction: Send AT Commands to BLE 4.0 Module From Android Phone

Today, I am going to show you how to send AT commands to Bluetooth Low Energy as called BLE 4.0 (There are BLE v4.1 and BLE v4.2) module by using your Android device which supports On-The-Go as called OTG option for example to detect a usb mouse indicator on your mobile phone by otg usb cable. This is the first time usage of Bluetooth Low Energy (BLE) module. This instructable is different because I am not using Arduino or Raspberry Pi board to send AT commands to BLE device, I am using my Android mobile phone to show you how powerful our Android devices are 🙂 (For HC05-HC07, read this)

NOTE: Charge your phone’s battery as %100 then begin!

The need list:

1. Android device with version bigger than v4.3with OTG support (Check your phone supports OTG or not)

2. OTG cable (Micro male usb pin input to usb type A female usb pin out)

3. Mini usb cable (Mini male usb pin input to usb type A male usb pin out)

4. FTDI FT232RL USB to TTL converter with conductive jumper plastic included

5. BLE 4.0 module (My module = SSID is BT05, LEVEL:3.3V, Power: 3.6V-6V, ZS-040, details are in next step)

Step 1: Make a Connection

Follow the diagram and make the connections between each part.

NOTE: When you run BLE module from your phone, your phone’s battery is going to go down a little bit more quick that’s because of external BLE module and FTDI module you attach and want to run both. So, charge up your phone before do this instructable.

NOTE: Your FTDI TTL converter should use 5V jumper. Check your converter’s logic converter level. It may 3.3V or 5V and there has to be GND between. Use 5V and GND to make short-circuit by a cable or jumper. Our bluetooth module supports 5V so we use 5V and GND pins together in same.

NOTE: If you are near with your computer you can use Tera Term program to send AT commands via usb cable to your bluetooth module over the cable. Your computer will recognize and opens a COM port and on Tera Term program, select serial port and write related COM port name and connect. (Check the picture about that)

NOTE: Baud rate is 9600

The app name is: Free USB Serial Term

Details: Click on the link above, sign in with your account, ass your mobile device to Google Play your account, download this application to your mobile phone. For more details, check the app page and learn what it supports as a hardware.

File is: 406 kilobytes

Step 3: While App Is Running

While app is running on your mobile phone:

1. Click on CR and LF things on the down-right side to enable both.

2. Click on right-top side’s wrench icon to go settings >> select 9600 as baud rate >> save and return to main page

3. Type AT command to BLE module then select OK after that. It should be response as OK.

On this step, let’s learn our module’s firmware version:

My firmware version is:

+VERSION=Firmware V3.0.6,Bluetooth V4.0 LE

Step 4: All Other AT Commands for Us

Now, test the AT commands as you like one-by-one:

AT+VERSION = +VERSION=Firmware V3.0.6,Bluetooth V4.0 LE

AT+ADDR = +ADDR=00:15:83:00:85:A9 (This is my device’s mac address)

AT+NAME = +NAME=BT05 (To change device name input AT+NAMEali, now the name is set as ali, then AT+RESET to enable new name, you can leave blank and use 13 character)

AT+ROLE = +ROLE=0 (Slave is 0 changes blink frequency rarely, Master is 1 changes blink frequency speedy, Slave-loop is 2 which loops from master to master)

AT+BAUD = +BAUD=4 (To change Baud Rate use AT+BAUDn n=1 for 1200, n=2 for 2400, n=3 for 4800, n=4 for 9600 (default), n=5 for 19200, n=6 for 38400, n=7 for 57600, n=8 for 115200, to enable, reset the module with AT+RESET)

AT+PIN = +PIN=000000 (To change pin AT+PIN123456 to enable AT+RESET)

AT+ORGL = Roll back to original settings

AT+RMAAD = If paired, release..

AT+PAIR=(12:34:56:78:90:10),60 = Try to pair this address (12:34:56:78:90:10) for 60 as a time unit.

NOTE: Other models of Bluetooth modules and other AT command details are here

Step 5: BONUS: Reading This Instructable

NOTE: This instructable’s step is aimed for visually impaired people to hear the sentences to learn what’s going on here. Watch the video, it explains all steps.

Did you make this project? Share it with us!

Источник

ADB Shell Commands

In this document

The Android Debug Bridge (adb) provides a Unix shell that you can use to run a variety of commands on an emulator or connected device. The command binaries are stored in the file system of the emulator or device, at /system/bin/.

Issuing Shell Commands

You can use the shell command to issue commands, with or without entering the adb remote shell on the emulator/device. To issue a single command without entering a remote shell, use the shell command like this:

Or enter a remote shell on an emulator/device like this:

When you are ready to exit the remote shell, press CTRL+D or type exit .

Using activity manager (am)

Within an adb shell, you can issue commands with the activity manager ( am ) tool to perform various system actions, such as start an activity, force-stop a process, broadcast an intent, modify the device screen properties, and more. While in a shell, the syntax is:

You can also issue an activity manager command directly from adb without entering a remote shell. For example:

Table 2. Available activity manager commands

Command

Description

start [options]

Start an Activity specified by .

Options are:

-D : Enable debugging.
-W : Wait for launch to complete.
—start-profiler : Start profiler and send results to .
-P : Like —start-profiler , but profiling stops when the app goes idle.
-R : Repeat the activity launch times. Prior to each repeat, the top activity will be finished.
-S : Force stop the target app before starting the activity.
—opengl-trace : Enable tracing of OpenGL functions.
—user | current : Specify which user to run as; if not specified, then run as the current user.

startservice [options]

Start the Service specified by .

Options are:

—user | current : Specify which user to run as; if not specified, then run as the current user.

force-stop

Force stop everything associated with

(the app’s package name).

kill [options]

Kill all processes associated with

(the app’s package name). This command kills only processes that are safe to kill and that will not impact the user experience.

Options are:

—user | all | current : Specify user whose processes to kill; all users if not specified.

kill-all

Kill all background processes.

broadcast [options]

Issue a broadcast intent.

Options are:

[—user | all | current] : Specify which user to send to; if not specified then send to all users.

instrument [options]

Start monitoring with an Instrumentation instance. Typically the target is the form / .

Options are:

-r : Print raw results (otherwise decode ). Use with [-e perf true] to generate raw output for performance measurements.
-e : Set argument to . For test runners a common form is -e [, . ] .
-p : Write profiling data to .
-w : Wait for instrumentation to finish before returning. Required for test runners.
—no-window-animation : Turn off window animations while running.
—user | current : Specify which user instrumentation runs in; current user if not specified.

profile start

Start profiler on

, write results to .

profile stop

Stop profiler on

dumpheap [options]

Dump the heap of

Options are:

—user [ |current] : When supplying a process name, specify user of process to dump; uses current user if not specified.
-n : Dump native heap instead of managed heap.

set-debug-app [options]

Set application

Options are:

-w : Wait for debugger when application starts.
—persistent : Retain this value.

clear-debug-app

Clear the package previous set for debugging with set-debug-app .

monitor [options]

Start monitoring for crashes or ANRs.

Options are:

—gdb : Start gdbserv on the given port at crash/ANR.

screen-compat [on|off]

Control screen compatibility mode of

display-size [reset| ]

Override emulator/device display size. This command is helpful for testing your app across different screen sizes by mimicking a small screen resolution using a device with a large screen, and vice versa.

Example:
am display-size 1280×800

display-density

Override emulator/device display density. This command is helpful for testing your app across different screen densities on high-density screen environment using a low density screen, and vice versa.

Example:
am display-density 480

to-uri

Print the given intent specification as a URI.

See the Specification for arguments.

to-intent-uri

Print the given intent specification as an intent: URI.

Specification for arguments

For activity manager commands that take a argument, you can specify the intent with the following options:

-a Specify the intent action, such as «android.intent.action.VIEW». You can declare this only once. -d Specify the intent data URI, such as «content://contacts/people/1». You can declare this only once. -t Specify the intent MIME type, such as «image/png». You can declare this only once. -c Specify an intent category, such as «android.intent.category.APP_CONTACTS». -n Specify the component name with package name prefix to create an explicit intent, such as «com.example.app/.ExampleActivity». -f Add flags to the intent, as supported by setFlags() . —esn Add a null extra. This option is not supported for URI intents. -e|—es Add string data as a key-value pair. —ez Add boolean data as a key-value pair. —ei Add integer data as a key-value pair. —el Add long data as a key-value pair. —ef Add float data as a key-value pair. —eu Add URI data as a key-value pair. —ecn Add a component name, which is converted and passed as a ComponentName object. —eia [, Add an array of integers. —ela [, Add an array of longs. —efa [, Add an array of floats. —grant-read-uri-permission Include the flag FLAG_GRANT_READ_URI_PERMISSION . —grant-write-uri-permission Include the flag FLAG_GRANT_WRITE_URI_PERMISSION . —debug-log-resolution Include the flag FLAG_DEBUG_LOG_RESOLUTION . —exclude-stopped-packages Include the flag FLAG_EXCLUDE_STOPPED_PACKAGES . —include-stopped-packages Include the flag FLAG_INCLUDE_STOPPED_PACKAGES . —activity-brought-to-front Include the flag FLAG_ACTIVITY_BROUGHT_TO_FRONT . —activity-clear-top Include the flag FLAG_ACTIVITY_CLEAR_TOP . —activity-clear-when-task-reset Include the flag FLAG_ACTIVITY_CLEAR_WHEN_TASK_RESET . —activity-exclude-from-recents Include the flag FLAG_ACTIVITY_EXCLUDE_FROM_RECENTS . —activity-launched-from-history Include the flag FLAG_ACTIVITY_LAUNCHED_FROM_HISTORY . —activity-multiple-task Include the flag FLAG_ACTIVITY_MULTIPLE_TASK . —activity-no-animation Include the flag FLAG_ACTIVITY_NO_ANIMATION . —activity-no-history Include the flag FLAG_ACTIVITY_NO_HISTORY . —activity-no-user-action Include the flag FLAG_ACTIVITY_NO_USER_ACTION . —activity-previous-is-top Include the flag FLAG_ACTIVITY_PREVIOUS_IS_TOP . —activity-reorder-to-front Include the flag FLAG_ACTIVITY_REORDER_TO_FRONT . —activity-reset-task-if-needed Include the flag FLAG_ACTIVITY_RESET_TASK_IF_NEEDED . —activity-single-top Include the flag FLAG_ACTIVITY_SINGLE_TOP . —activity-clear-task Include the flag FLAG_ACTIVITY_CLEAR_TASK . —activity-task-on-home Include the flag FLAG_ACTIVITY_TASK_ON_HOME . —receiver-registered-only Include the flag FLAG_RECEIVER_REGISTERED_ONLY . —receiver-replace-pending Include the flag FLAG_RECEIVER_REPLACE_PENDING . —selector Requires the use of -d and -t options to set the intent data and type.

You can directly specify a URI, package name, and component name when not qualified by one of the above options. When an argument is unqualified, the tool assumes the argument is a URI if it contains a «:» (colon); it assumes the argument is a component name if it contains a «/» (forward-slash); otherwise it assumes the argument is a package name.

Using package manager (pm)

Within an adb shell, you can issue commands with the package manager ( pm ) tool to perform actions and queries on application packages installed on the device. While in a shell, the syntax is:

You can also issue a package manager command directly from adb without entering a remote shell. For example:

Table 3. Available package manager commands.

Command	Description
list packages [options]	Prints all packages, optionally only those whose package name contains the text in . Options: -f : See their associated file. -d : Filter to only show disabled packages. -e : Filter to only show enabled packages. -s : Filter to only show system packages. -3 : Filter to only show third party packages. -i : See the installer for the packages. -u : Also include uninstalled packages. —user : The user space to query.
list permission-groups	Prints all known permission groups.
list permissions [options]	Prints all known permissions, optionally only those in . Options: -g : Organize by group. -f : Print all information. -s : Short summary. -d : Only list dangerous permissions. -u : List only the permissions users will see.
list instrumentation	List all test packages. Options: -f : List the APK file for the test package. : List test packages for only this app.
list features	Prints all features of the system.
list libraries	Prints all the libraries supported by the current device.
list users	Prints all users on the system.
path	Print the path to the APK of the given .
install [options]	Installs a package (specified by Options: -l : Install the package with forward lock. -r : Reinstall an exisiting app, keeping its data. -t : Allow test APKs to be installed. -i : Specify the installer package name. -s : Install package on the shared mass storage (such as sdcard). -f : Install package on the internal system memory. -d : Allow version code downgrade.
uninstall [options]	Removes a package from the system. Options: -k : Keep the data and cache directories around after package removal.
clear	Deletes all data associated with a package.
enable	Enable the given package or component (written as «package/class»).
disable	Disable the given package or component (written as «package/class»).
disable-user [options] Options: —user : The user to disable.
grant	Grant permissions to applications. Only optional permissions the application has declared can be granted.
revoke	Revoke permissions to applications. Only optional permissions the application has declared can be revoked.
set-install-location	Changes the default install location. Location values: 0 : Auto—Let system decide the best location. 1 : Internal—install on internal device storage. 2 : External—install on external media. Note: This is only intended for debugging; using this can cause applications to break and other undesireable behavior.
get-install-location	Returns the current install location. Return values: 0 [auto] : Lets system decide the best location 1 [internal] : Installs on internal device storage 2 [external] : Installs on external media
set-permission-enforced [true\|false]	Specifies whether the given permission should be enforced.
trim-caches	Trim cache files to reach the given free space.
create-user	Create a new user with the given , printing the new user identifier of the user.
remove-user	Remove the user with the given , deleting all data associated with that user
get-max-users	Prints the maximum number of users supported by the device.

Taking a device screenshot

The screencap command is a shell utility for taking a screenshot of a device display. While in a shell, the syntax is:

To use the screencap from the command line, type the following:

Here’s an example screenshot session, using the adb shell to capture the screenshot and the pull command to download the file from the device:

Recording a device screen

The screenrecord command is a shell utility for recording the display of devices running Android 4.4 (API level 19) and higher. The utility records screen activity to an MPEG-4 file.

Note: Audio is not recorded with the video file.

A developer can use this file to create promotional or training videos. While in a shell, the syntax is:

To use screenrecord from the command line, type the following:

Stop the screen recording by pressing Ctrl-C, otherwise the recording stops automatically at three minutes or the time limit set by —time-limit .

To begin recording your device screen, run the screenrecord command to record the video. Then, run the pull command to download the video from the device to the host computer. Here’s an example recording session:

The screenrecord utility can record at any supported resolution and bit rate you request, while retaining the aspect ratio of the device display. The utility records at the native display resolution and orientation by default, with a maximum length of three minutes.

There are some known limitations of the screenrecord utility that you should be aware of when using it:

Some devices may not be able to record at their native display resolution. If you encounter problems with screen recording, try using a lower screen resolution.
Rotation of the screen during recording is not supported. If the screen does rotate during recording, some of the screen is cut off in the recording.

Table 4. screenrecord options

Options	Description
—help	Displays command syntax and options
—size	Sets the video size: 1280×720 . The default value is the device’s native display resolution (if supported), 1280×720 if not. For best results, use a size supported by your device’s Advanced Video Coding (AVC) encoder.
—bit-rate	Sets the video bit rate for the video, in megabits per second. The default value is 4Mbps. You can increase the bit rate to improve video quality, but doing so results in larger movie files. The following example sets the recording bit rate to 6Mbps:
—time-limit	Sets the maximum recording time, in seconds. The default and maximum value is 180 (3 minutes).
—rotate	Rotates the output 90 degrees. This feature is experimental.
—verbose	Displays log information on the command-line screen. If you do not set this option, the utility does not display any information while running.

Other shell commands

For a list of all the available shell programs, use the following command:

Help is available for most of the commands.

Table 5 lists some of the more common adb shell commands.

Table 5. Some other adb shell commands

Источник

Use at commands in android