Path: ...!news.mixmin.net!news.swapon.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.mobile.android
Subject: Re: Tutorial: How to output Android system information to a
 text/pdf/html file
Date: Mon, 19 May 2025 08:40:35 +0200
Lines: 70
Message-ID: <m9022tFoppuU2@mid.individual.net>
References: <100ej34$u63$1@nnrp.usenet.blueworldhosting.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net /Xy9V/TCWQu34f21d+PGzAaWqybsd3U5u+wN8IfSPJ62BrhI8V
Cancel-Lock: sha1:i/1D6LYKkYwOF94CSg//Lr1ZJoo= sha256:UCQfNruzfnBIiJRB18BVV2R20CIWDMCIGSUjy8P3vmw=
Content-Language: en-US, de-DE
In-Reply-To: <100ej34$u63$1@nnrp.usenet.blueworldhosting.com>
Bytes: 4014

Marion, 2025-05-19 08:28:

> Tutorial: How to output Android system information to a text/pdf/html file
> (As always, please improve by adding value where you know more than I do.)
> 
> So as to not tangent a recent thread similar to this topic, here's a 
> quick tutorial I just wrote for those who wish to save device info to a file.
> 
> ADB, of course, can report your system information to a file, e.g., 
>  C:\> adb shell getprop > about_phone_info.txt
> For specific keywords, one can grep for the desired strings:
>   C:\> adb shell getprop | findstr version.release
>   C:\> adb shell getprop | findstr ro.product.model
>   C:\> adb shell getprop | gsm.version.baseband
>   etc.
> But the information isn't always in easily understood format.
> 
> For more easily understood text, html & PDF system-information files, 
> I just tested these freeware system-reporting apps below for the team.
> 
> Aida64 (location does not appear to be user selectable)
>  <https://play.google.com/store/apps/details?id=com.finalwire.aida64>
>  3dots > Save Report 
>  Saves default output in this location with this naming convention:
>  /storage/emulated/0/Android/data/com.finalwire.aida64\files\report-2025-05-18-22-26-59.txt
> 
> DevCheck (location is user selectable)
>  <https://play.google.com/store/apps/details?id=flar2.devcheck>
>  3dots > Export
>  Saves default output anywhere with this type of naming convention:
>  C:\> adb shell ls /storage/emulated/0/Download/DevCheck*
>  C:\> adb pull /storage/emulated/0/Download/DevCheck-20250518-2305.txt
> 
> DeviceInfo (location & type is user selectable)
>  <https://play.google.com/store/apps/details?id=com.toralabs.deviceinfo>
>  3dots > Export details > Report Type > [x]Text [_]PDF
>  C:\> adb shell ls /storage/emulated/0/Download/Device-Info-Report*
>  C:\> adb pull /storage/emulated/0/Download/Device-Info-Report.txt
>  C:\> adb pull /storage/emulated/0/Download/Device-Info-Report.pdf
> 
> Device Info HW (requires pro license to generate the reports)
>  <https://play.google.com/store/apps/details?id=ru.andr7e.deviceinfohw>
>  Only pro version can create the reports
>  3dots > Info center > Create report > (o)HTML (_)PDF 
> 
> Free system-reporting apps which do not appear to save output to a file are
>  Treble Info <tk.hack5.treblecheck>
>  Inware <com.evo.inware>
>  CPU Info <com.kgurgul.cpuinfo>
>  CPU-Z <com.cpuid.cpu_z>
> 
> As always, I write these tutorials as a voluntary public service, and 
> since I'm always trying to learn more, please add value where you can.
> 
> That way the entire team increases our extensive tribal knowledge level.


My addition here: to use ADB you need a working setup of ADB on the host
computer and a connection via USB (newer devices also support ADB via
WiFi which requires to know the IP address of the device in the local
network). The device also has to allow "USB debugging" which can be
enabled in the developer options of the device, otherwise you can't do
anything at all using ADB.

Also see: <https://developer.android.com/tools/adb?authuser=1&hl=en>


-- 
Arno Welzel
https://arnowelzel.de