Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
92 views

Adb Commands

The document provides instructions for using ADB (Android Debug Bridge) to communicate with and diagnose issues on an Android device. It describes how to set the USB role to device mode, open a command prompt, gain root access via ADB shell, pull logs and data from the device to a PC directory, reboot into recovery mode, capture logcat logs, use hlogutil to control log verbosity, generate an ADB bug report, dump system data using dumpsys, use screencopy to diagnose display issues, and provides tips for diagnosing various issues like RVC problems, media hub issues, and EOL failures.

Uploaded by

Jonathan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
92 views

Adb Commands

The document provides instructions for using ADB (Android Debug Bridge) to communicate with and diagnose issues on an Android device. It describes how to set the USB role to device mode, open a command prompt, gain root access via ADB shell, pull logs and data from the device to a PC directory, reboot into recovery mode, capture logcat logs, use hlogutil to control log verbosity, generate an ADB bug report, dump system data using dumpsys, use screencopy to diagnose display issues, and provides tips for diagnosing various issues like RVC problems, media hub issues, and EOL failures.

Uploaded by

Jonathan
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

ADB METHOD

Always be sure that the USB Role is set to Device mode. Open your command prompt
and start to programming.

Pull Data
adb devices %% Android device is recognized by PC
adb root
adb shell %% command used to communicate with the android device
(radio), allows: install/Uninstall apps, transfer files and reboot the device)
su %% Always run “su” after running “adb shell”, is a utility to
give user permission to run system commands.
cd c:\user\directory %% open chosen directory
adb pull /data/logs %% that’s responsible to pull data and put it into the chosen
directory
ls /data/logs/ %% it’s shows all logs in the radio
We also can be requested to pull a different data, Ex: ANR
ls /data/ chosen data %% Choose a request data
After pull the data, write
exit
If the radio be in a really bad state, we have to restart it. So, to reboot and run a recovery
kenel at the radio. After the rebooting, A black screen will appear in the radio.
adb reboot recovery %factory resert

Kernel Logging

Adb shell
Dmesg > /sdcard/dmesg_log.txt % include the file
ls/sdcard/ % see if was included
exist
Pulling the kernel logs
adb root
cd c:\user\ % open chosen directory
adb pull /sdcard/dmesg_log.txt % pull data
Now the data is on the chosen directory, check it. It’s necessary to remove the file.
adb shell
rm /sdcard/dmesg_log.txt
ls /sdcard/ % see if was removed

There is many IPC communication channels some of them are dedicated. The command
to choose the required channel is:
enabletrace(#) > /dev/ipcdebug % # - replace the channel here. It is not so simple, if
necessary ask more information about it.

LOGCAT
Required for almost all issues, contains four separate buffers (physical memory storage,
temporarily). Main, event, radio, system and crash data’s. Also stored as “aplogs” in
/data/logs saves last 100 MB, because it is lower than aplogs. If not all aplogs was
necessary the Harman time can request the logcat’s.
adb shell
logcat > /sdcard/logcat_logs.txt
ls /sdcard/
exit

HLOGUTILS
It is a Harman internal utility to control the verbosity of ceratin features or tags in
logcat.
hlogutil –i tags % info level (the navd is set to info)
hlogutil –t NAVD –l VERBOSE % change navd tag to verbose
logcat | grep NAVD % to capture log (either send it to a file in sdcard).

ADB – BUG REPORT


It provide a complete system snapshot of the system, it means gives everything is going
on the device.
 SMAP
 DUMPTRACE
 ALL APLOGS
 DMESG
 IPTALBES
 MEMORY/CPU INFORMATION
 ALL ANR CRASHES
 VIRTUAL MEMORY STATISTICS
 LIST OF OPEN FILES
 BLOCSTART
To see the bugreport on command prompt, type the following commands:
adb devices
adb root
adb shell
bug
It can takes about 8 minutes to get ready. If you want to see the CPU load setting, type:
top

DUMPSYS DATA
It provides key information regarding certain services/state of the unit. The frequently
used commands:
 dumpsys meminfo
 dumpsys diskstats
 dumpsys packages
 dumpsys features
 dumpsys location

Additional Item
There is a powerful tools to helps the diagnose tests, it’s called screencopy. To allows
the screencopy access, you should type the following commands:
adb devices
Adb root
After that, just open the screencopy executable. That’s really powerful because It can be
used like a test method, if the screencopy works it means that the problem is on the
LVDC cable or display (we are going to see more about it).
Using the screencopy:
Apps Menu -> Engineering Mode
There you can see the software version number, also the serial number.
There is a software; called AxB, softcore on firmwareHubEmulator. Software to reduce
the bluebox, using the NEC flasher mode (Still need more information’s about it).
TIPS FOR DIAGNOSING ISSUES

 Vehicle Configuration Issuses


Mid-Atlantis CAN Arch means head units most be proxied ahead of time to hard code
features into the HU.
- Use mid-atlantis RAFT (set tester Present);
- Enable AME mode (send a message “22 20 23”).

 Display Issues
If there is an issue with the display, check if the backlight is visible during ing on.
- If visible then CAN BUS issues or video signal issue from LVDS can be culprits;
- If not visible then power is not being supplied to the display or maybe
defective.
Screen copy is a powerful tool to determine if HU is sending proper video image to the
display.
- ADB connection must be available with HU;
- Run screencpy batch file;
- If image is able to be shown on laptop than black dispay issue could reside with
LVDS cable, improper sseding at contact points, bent pins or display.

 RVC issues

There are two main types of cameras:


- Analog – Connection part of main tri-herness;
- Digital – Connection are tied to red and tan fakra connectos.
If dealing with RVC issues, for example, no RVC or improper RVC image when reverse is
in gear, adb into the HU and send the following command
dd if=/dev/vechicle_camera_config count=l bs=256 | od –tx –v –Ax

 Media Hub Issue


Harman must support media hub functionality w/ multiple suppliers
- Bring USB stick with media files
- Determine if HUB is on and powered when ign on
- ADB connection is dependent on connecting to correct USB port
 EOL Issues
Check to see if EOL failure is persistent or disappears after multiple retries

- If EOL failure is reproducible, pay attention to detail


- Determine if the EOL failure is at the beginning of the rest run, vs during the
test run
- HU needs time to launch diagnostic service after ign on
 And this varies between S2R and boot
- Record which EOL test fails
- Determine if other vehicles are failing the same EOL test
- Call Harman tier I or tier II support to bring attention to failure.

You might also like