An ideal tool for developers, customer support and user.
NOTE: this app doesn't send your ID to the internet so your information is safe.
For paranoid users, you can get Device ID without any network permission at :
This will disable Local IP Address and MAC address.
Google Services Framework Key ID
Subscriber ID (IMSI)
SIM Card Serial
WiFi MAC Address
Ethernet MAC Address
Bluetooth MAC Address
Bluetooth Paired MAC Address
Device Build Fingerprint
Please leave some suggestion.
Permission Explanation :
INTERNET is used to get your local IP address
BLUETOOTH is used to get your Bluetooth MAC address
READ_PHONE_STATE is used to get your IMEI, IMSI and SIM Serial
ACCESS_WIFI_STATE and ACCESS_NETWORK_STATE is used to get your MAC address
READ_GSERVICES is used to get your Google Services Framework ID
You are allowed to disable the permission using root app such as Permission Manager if you are paranoid
For user that wanted to get both SIM Serial in DUAL SIM Phone, The default SDK does not have support to handle dual SIM phones. The function will only return one number, most likely from the first active SIM card.
Facebook : https://www.facebook.com/evozi/
Beta Testing Group :
Instead of rating 1 or 2 star,please email to email@example.com or leave a comment so that we can fix or improve it.
Another purpose is to check DUAL-IMSI behavior since the app can detect IMSI change automatically.
When the SIM is inserted the IMSI is saved to the phone's memory automatically and then if the first IMSI is switched with the second IMSI or the new SIM is inserted the app will display the pop-up screen to notify that the IMSI is changed.
The parameters collected by Mobile Analyzer application can be separeted in three groups:
- SIM Card: PLMN, Serial Number, SPN, IMSI, Voice Mail Number, SIM Card State.
- Mobile Phone: IMEI, IMEI-SV, MMS User Agent, MMS UA Profile URL, .
- Network information: Data State, Network Type, PLMN, Name of the Network, Call State, Roaming, Signal Power, LAC/TAC, GPS Position and Cell ID.
With Mobile Analyzer is possible to collect logs and save it on CSV Excel file.
Network Info: Network Provider, Network Type 2G, 3G, LTE Etc, Operator ID, Data State.
Device Details: IMEI Number, Device Type GSM/CDMA, Model Name, Manufacturer, Brand, Hardware Info.
Operating System Info: OS Name like Jellybean, Kit Kat, SDK Version, Android Version, Binary Type
Sim Contacts: List of Contacts stored in SIM
Debug your apps. Find error stacktraces. See what your phone is saying about you behind your back. It's all there in the system log, aka logcat!
What makes CatLog stand out over similar apps?
* Color-coded tag names
* Easy-to-read column display
* Real-time search
* Recording mode (with widget)
* Save & open from SD card
* Send logs as email or attachment
* Auto-scrolls when at the bottom of the screen (just like tail -f)
* Search autosuggestions & saved filters
* Select parts of logs
* Open-source and ad-free
View color-coded, scrolling (tailed) Android device (logcat) logs directly from your phone. No USB, adb, or emailing necessary.
Set log format / level / buffer, filter logs by regex, clear log file, save to SD.
Share logs via any application that handles plain text or HTML sharing, including Gmail, Email, Pastedroid, Bluetooth, and others.
Install application Pastedroid to share logs via pastebin. Ensure HTML output is disabled in preferences as this only supports plain text logs.
aLogcat supports near full control through intents. Broadcast to start the app, save log snapshots, share logs, or make periodic saves.
Note: the periodic save feature was removed as of version 2.5. Consider the application aLogrec if you need to continuously record logs to the SD card.
With contributions by,
Please note: From Android 4.1 onwards ANY logcat app needs root access in order to show logs.
New sliding side menus (update 1.4):
the UI has been dramatically improved and reorganized in side menus, swipe from the left side to the right to access the navigation menu and switch between the main features, swipe from the right side to the left to access the list of your saved logcats, from there open, send or delete your logs.
Introducing "Floating Logcat" (update 1.1):
a new wonderful feature powered by StandOut, it allows you to keep the logcat on top right while you're working on your device, perfect for your tests! the logcat is shown inside a window you can move, resize and even minimize, just like a desktop one.
* Read live logcat
* Pause and resume
* Record (even in background)
* Send logs via mail
* Apply filters (priority level, format, etc.)
* Search box for quick filtering
* Many options to configure the logcat
* Read the kernel's debug messages (dmesg)
* UI straightforward, the controls you need at your fingertips
* New "Per-app Logcat" feature!
* Revolutionary "Floating Logcat" feature!
* Floating window resizable even with pintch-to-zoom
- In order to start a new Floating Logcat session tap the last button on the right (bottom bar).
- In order to resize the Floating Logcat drag the bottom-right corner of the window.
Starting from version 1.3, devs can use intent actions and extras in order to launch the
logcat recorder directly from their apps:
"scd.lcex.ACTION_REC" start recording
"scd.lcex.ACTION_STOP" stop recording and service associated
"scd.lcex.EXTRA_FILTER" logcat filter (string, optional), use in conjunction with ACTION_REC
Details Shown by Phone Info - Android System and Hardware Information:
► Carrier Information
See your phone number, carrier, IMSI, IMEI, MEID, MCC, and MNC
► Screen Information
Get screen resolution, density, and size settings
► Software Versions
Build Serial, Build ID, Bootloader Version, Build Tags, and SDK version
CPU, Model Number, and Manufacturer
☆ Accurate and Reliable Works on many versions of Android and many device models.
☆ Fast and Simple Get the information you need, quickly.
I wrote this tiny utility because I was eager to find my phone model and IMSI, but don't know how. If you find it is useful, at least one time, please support me. Thanks you!
The IMEI (International Mobile Equipment Identity) is a unique number to identify GSM, WCDMA, and iDEN mobile phones, as well as some satellite phones.
Application allows you to check details for any IMEI.
Please contact via email if app crashes on your device or you wish to report a bug. This way we can exchange details about your issues. Giving app bad review because it does not work on your device helps no one. Thanks.
Root is required for Android 4.1+, and recommended for all versions.
Log types supported:
* Kernel logs (dmsg)
* Last kernel log (last_kmsg, if device supports it)
* Main log (Logcat)
* Modem log
* Event logs
After taking logs, it compresses them into a single zip, and allows you to share or upload them right away - great for helping debug system issues.
You can also include notes within the zip, and append up to 10 characters to the file name.
New feature in v1.2: Grep the logs for a string. This will run the logs through grep before adding them to the zip. This is case sensitive! It will also automatically add a line to the end of the notes describing which logs and what string was used.
All the source is available at https://github.com/Tortel/SysLog
Licensed under the GNU General Public License, version 2.
Uses libsuperuser by Jorrit 'Chainfire' Jongma, available at https://github.com/Chainfire/libsuperuser and the AppCompat v21 library.
The log scrubbing utility came from the CyanogenMod bug report tool
And you can collect logcat by background process.
The feature of this application is described below.
- A long message of log will be displayed in multiple-line.
Therefore, the message of log can be checked at a glance.
- A search character string and a tag character string are recorded as a history.
later, you can refer to this history so you can input easily.
- In the background, you can collect logs.
There is a filter specification function for narrowing down collecting logs.
And there is an notification function at the time of detecting the character string specified beforehand.
- Starting background collection automatically at boot end is enabled. (Auto start on BOOT end)
- In the log detailed screen (that appears at long touch of a log line), a filter setting, cooperation with a search function, and cooperation with a mailer are possible.
- Added 'Menu Bar' which is located on the left end of a screen.
- Radio log and events log can be collected.
- Cut filter by tag is possible.
- Set of filters can be memorized.
- Narrowing is possible.
- Maximum of buffer size of reading from system is 10,000 lines.
(Note : maximum of buffer size of reading from file is 30,000 lines.)
A feature is built-in to test your current configuration without rebooting. The lines shown in test mode may be limited and relatively static, this does not reflect exact boot time behavior as much as it just shows you that it works and how big the text will be.
Note that LiveBoot will only show up after the data partition is mounted. If you need to enter a decryption key or pattern at boot, it will not show up until you have done so.
This app does not only require root, it requires specifically SuperSU version 2.40 or newer, due to how the boot-time code is launched. Alternatively, the app will try to function for otherwise rooted firmwares that support init.d, but this is not officially supported and it cannot be guaranteed to work.
Officially the app supports 4.3+ and newer, but really it is aimed at 5.0 firmwares. Regardless of 4.3, 4.4, or 5.0, the app may work on your device or it may not. I've gotten it to work on a bunch of my own devices on various firmwares, but not on all. Even if the test run functionality works, this does not necessarily mean it will actually work during boot. It usually does, but not always.
This does indeed also mean I cannot guarantee continued operation - even if it works for you today, it may fail your next firmware update. If that is an issue for you, then you should definitely not update to Pro.
The risk of bootloops is extremely low, but not completely non-existent. Should a bootloop occur, removing either the app's APK or /system/su.d/0000liveboot through recovery should fix the problem.
The app writes to /system, as such your firmware must allow this. There is no recovery-based install option at this time.
There's an in-app purchase to upgrade to Pro, which supports my developments, and unlocks the transparency option as well as logcat buffer and format selection.
Of course, if you have one of the paid variants of the old live logcat or live dmesg boot animations from all those years ago installed, this will also enable Pro mode.
Like some of my other apps these days, if you don't have Google Play but still managed to install the APK, this will also enable Pro mode.
Last but not least, if you simply don't want to pay for it, there's also a button to enable Pro mode.
If /system/su.d/0000liveboot.script exists (chmod 0644, not 0700 like other files in /system/su.d/ !), this script will be run instead of logcat and dmesg, and its output will be shown in white (stdout) and red (stderr).
Please see the official app thread on XDA-Developers.com here: http://forum.xda-developers.com/android/apps-games/liveboot-t2976189
After the program start. When any APP crashes, it will start to send the log. Let programmers to find out the problem.
If run this app and not get any crash log, try
"adb shell pm grant crashLog.cutebabyTW android.permission.READ_LOGS"
and reboot to fix permission.
Users can use this app to check the status of remote android devices (like webcams). Or to follow with their PC what is going on with their device (no more complicated sdk/adb setup required!). No root required. Help developers to track down bugs by sending logfiles with your error reports. When sharing logfiles: please check if they contain any private data!
Developers debugging remote apps without computer connection can use this to monitor their app. Also they can use an easy Intent (com.dngames.remotelogcat.LOG) or send SMS to get a logfile via this app. You can also just add an Thread.setDefaultUncaughtExceptionHandler(...); to your app and then log with a remotelogcat.LOG Intent if it is installed. So no need to include libs like ACRA in your APP if you want to debug only sometimes.
Mobile data connection debugging is now possible, but without WIFI connection you need your own server with PHP or my app AutoShare to publish the logfiles.
This is intended to run in the background to debug other apps - to stop the background service please disable it in the settings!
Just install it and if you reach a Website with malicious code inside there will be a popup asking you wich app to launch. Just select "use as standard" an choose NoTel:URL as app and you will be fine.
Starting with Version 1.1 of the App, malicious USSD Codes are shown within a popup Window. To gain best protection there is no way to execute USSD codes. If you klick on a valid phone number within a webpage or received by barcode you are able to execute the request if your Android OS Version is >= Ice Cream Sandwich.
Below this Version there is no way to directly rout the number to the dialer, so you need to do this manually by typing the number in the dialer.
There is no need to start the App manually. If you do so, there will be an explaining Popop now.
Everything will went automatically if the app is just installed.
Detailed Information can be found on my Website:
Here you will also find urls and barcode for testing
Keywords: USSD, security
Basis des ganzen ist ein Artikel der im Print Magazin Android-User.de unter meiner Mitwirkung entstanden ist und Apps ins Visir nimmt, die mit nahezu krimineler Energie den Play-Store und andere App Stores überschwemmen. Klares und einziges Ziel dabei, BernutzerInnen mit Werbeeinblendungen und PushWerbung zu überschütten.
Die meisten der direkt in diesem Artikel angeführten Apps sind bereits aus dem Google Store entfernt worden, jedoch leben diese Apps in sekundären Appstores weiter und verbreiten sich ungewollt schnell auf unseren Smartphones.
Um Euch eine gewisse Sicherheit zumindest gegen die zur Zeit entdeckten, schädlichen Apps zu bieten, wurde die Idee zu dieser App geboren. Im Grunde eine einfache Sache, von einer vertrauenswürdigen Seite wird eine Liste mit App-Packagenamen geladen und das Smartphone wird danach dahingehend überprüft ob eine der in dieser Liste angeführten Apps installiert ist. Nicht mehr und nicht weniger.
Ihr könnt selber entscheiden, ob ihr die App dann deinstallieren wollt oder nicht.
Internet: Benötigt um die Liste der bekannten Packages herunter zu laden.
Access_Network_State: Notwendig um eine funktionierende Internetverbindung abzufragen.
Link zum Artikel bei Android-User.de:
Link zur Entstehung dieser App:
Mein Dank richtet sich an Marcel Hilzinger vom Magazin Android-User sowie an den Forensic Experten Marko Rogge. Erst diese fruchtbare Zusammenarbeit ermöglichte diese App!
NoStalk will resume normal RingingMode after this. Every time "unknown Caller ID" is displayed your Android will keep silent up from now.
Update to V1.4 New German language pack and more.
Darüber hinaus demonstriert diese App wie es möglich ist, Daten aus einer App ins Internet zu übertragen, ohne die dafür notwendige Berechtigung "Vollständiger Internetzugriff" zu haben.
In dem dazugehörigen Blog wird dargelegt, welche IDs es auf den Smartphones gibt und warum man Vorsicht walten lassen sollte sie im Netz zu verteilen.
Diese App benötigt die Berechtigung "READ_PHONE_STATE" (TELEFONSTATUS UND IDENTITÄT ABRUFEN)
Dieses wird lediglich verwendet um die Daten anzuzeigen. Die ausgelesenen Daten werden weder ins Log geschrieben noch an Dritte übertragen.
Bei Fragen zu dieser App kann jederzeit ein Eintrag zu dem entsprechenden Artikel in meinem Blog gestellt werden. Dort kann ich auch gezielt und direkt antworten.
Die Idee dazu wurde auf der Android-Plattform AndroidPIT geboren.
Jannik - Die Vorlage als Windows App
Sven Manzke - Änderung bei der Edit Feld Problematik. Cooler Tipp :)
Attention, this app won't show up in normal application folder. It's visible only in the manage application list.