Path: ...!weretis.net!feeder9.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!nnrp.usenet.blueworldhosting.com!.POSTED!not-for-mail
From: Marion <marion@facts.com>
Newsgroups: comp.mobile.android
Subject: Tutorial: How to output Android system information to a text/pdf/html file
Date: Mon, 19 May 2025 06:28:53 -0000 (UTC)
Organization: BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID: <100ej34$u63$1@nnrp.usenet.blueworldhosting.com>
Injection-Date: Mon, 19 May 2025 06:28:53 -0000 (UTC)
Injection-Info: nnrp.usenet.blueworldhosting.com;
	logging-data="30915"; mail-complaints-to="usenet@blueworldhosting.com"
User-Agent: MacSOUP/2.8.5 (ea919cf118) (Mac OS 10.12.6)
Cancel-Lock: sha1:fME1cvtqqQ7OOstFBV0HMrsY18o= sha256:d4/G0Rqt8yX6zkJ5YMBYPZBsXehAJqX6tzk7bGMayyw=
	sha1:d9XbI6OTqRw3lt18yCqHv6lmHCw= sha256:0cBuT+TJwkDMoRl07+sKGvxqe8fCXmuXk8RH05ukta8=
Bytes: 3506
Lines: 52

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.