![Logcat [NO ROOT] cover image](https://cdn.aapks.com/image/9c00fbca57cc4f7487d9e8c447582587_fgraphic.png?w=768)
UpdatedNov 8, 2025
PublishedJun 3, 2022
Packagecom.tananaev.logcat
MD5b13db1d14544aea56196c082cdbd5a32
SHA1 (signer)AA:75:28:03:41:9B:66:BC:6D:5C:FC:D6:1A:7C:88:93:5F:FE:55:11
Signed byCN=Anton Tananaev, OU=Unknown, O=Unknown, L=Unknown, ST=Unknown, C=Unknown
Architecturesx86, x86-64, armeabi-v7a, arm64-v8a
Malware scanTRUSTED
Contact[email protected]
What's new
Bug fixes and improvements
Description
PLEASE READ DESCRIPTION.
Read Android logs without root access. The app uses remote debugging to connect to phone local ADB daemon. Configuring remote debugging on a phone can be challenging and requires some technical expertise. It has to be done once and after each device reboot.
Enable USB debugging first on your device. Navigate to Settings > About Phone and tap Build number seven times. Go back, access the Developer options menu and check USB debugging option.
Next step is to enable remote debugging. You need to have Android SDK installed on your computer. Connect your phone via USB cable and run following adb command:
adb tcpip 5555
Disconnect USB cable before trying to use the app. Some phones have problems handling network ADB connection when they are connected via USB as well.
Sometimes establishing connection to ADB hangs and requires killing and restarting the app. It seems to be a problem with ADB daemon itself and not the app issue.
Read Android logs without root access. The app uses remote debugging to connect to phone local ADB daemon. Configuring remote debugging on a phone can be challenging and requires some technical expertise. It has to be done once and after each device reboot.
Enable USB debugging first on your device. Navigate to Settings > About Phone and tap Build number seven times. Go back, access the Developer options menu and check USB debugging option.
Next step is to enable remote debugging. You need to have Android SDK installed on your computer. Connect your phone via USB cable and run following adb command:
adb tcpip 5555
Disconnect USB cable before trying to use the app. Some phones have problems handling network ADB connection when they are connected via USB as well.
Sometimes establishing connection to ADB hangs and requires killing and restarting the app. It seems to be a problem with ADB daemon itself and not the app issue.
Required features
- Faketouch android.hardware.faketouch
Permissions (10)
Logcat [NO ROOT] requests the following Android permissions:
- Access Adservices Ad Id android.permission.ACCESS_ADSERVICES_AD_ID
- Access Adservices Attribution android.permission.ACCESS_ADSERVICES_ATTRIBUTION
- Access Adservices Topics android.permission.ACCESS_ADSERVICES_TOPICS
- Access Network State android.permission.ACCESS_NETWORK_STATE
- Foreground Service android.permission.FOREGROUND_SERVICE
- Internet android.permission.INTERNET
- Wake Lock android.permission.WAKE_LOCK
- Finsky Permission Bind Get Install Referrer Service com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
- Gms Permission Ad Id com.google.android.gms.permission.AD_ID
- Com Tananaev Logcat Dynamic Receiver Not Exported Permission com.tananaev.logcat.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION