I want to know can we attach a debugger to an app running on the smartphone which is published over Google Play Store ***without modifying the original app***? The reasons for asking this is by default the app which is there over Google playstore are non debuggable, i.e in the AndroidManifest.xml file, either they won't have android:debuggable flag or if it is, then it will be set to **false**

I have 2 Android 14 phones. Both have Wireless Debugging enabled. Both are paired with the adb server PC. All devices are connected to the same WLAN. One of the phones always uses a static port in IP Address & Port menu entry. The other does not, it always randomizes the port. Network & Debug Networking options are the same for both phones. How to I make it keep the port static **on phone** (NOT with adb tcpip, it will not work in this case at all)? Phones: 1. OnePlus 8 Pro (instantnoodlep, IN2020 CN), Android security update 2024-09-05 - uses dynamic port 2. Motorola moto g(7) plus (lake), Android security update 2024-09-05 - uses static port

Sometimes I get asked for a LogCat. **What is this?**
**What is it supposed to do?**
**How can I get it?**

This is related to an issue with Android custom ROMs on the legacy device the LG G4, since the move to A12 and A13. This doesn't occur on any version below A12. I need your help with debugging the black screen issue on telephone calls in A13 on the LG G4. As soon as we accept a telephone call, the screen goes black, and the only way to interact with the phone is via the power button. There is some issue with the proximity sensor on this device since A12+. However, any testing app I have used states that the proximity sensor is detected and works correctly but no ROM seems to make use of it. We have been doing a lot of testing to help try and find a root cause. We noticed that if the headset is plugged in, the black screen issue doesn't occur. This behaviour is explained in [ProximitySensor.java](https://github.com/LineageOS/android_packages_apps_Dialer/blob/lineage-20.0/java/com/android/incallui/ProximitySensor.java#L205) : >Proximity wake lock will be released if any of the following conditions are true: the audio is routed through bluetooth, a wired headset, or the speaker; the user requested, received a request for, or is in a video call; or the phone is horizontal while in a call. We took some logs of phone calls, and I noticed, when filtering on proximity in the logs, we have two different situations: - telephone call with headphones (log filtered by proximity) => screenOnImmediately: true - telephone call No headphones (log filtered by proximity and PID of dialer) => screenOnImmediately: false I think we need to debug the code to find out why the proximity sensor doesn't reply correctly, or isn't queried correctly. I think the important parameter is PROXIMITY_SCREEN_OFF_WAKE_LOCK. See [ProximitySensor.java, line 69](https://github.com/LineageOS/android_packages_apps_Dialer/blob/lineage-20.0/java/com/android/incallui/ProximitySensor.java#L69) and [ProximitySensor.java, line 198](https://github.com/LineageOS/android_packages_apps_Dialer/blob/lineage-20.0/java/com/android/incallui/ProximitySensor.java#L198) . I see references to the parameter PROXIMITY_SCREEN_OFF_WAKE_LOCK in frameworks_base and frameworks_native.

I am testing a kiosk Android application. This is a food-ordering kiosk application. The device's RAM is 8GB. The flow of the application is: The user comes to the app. At first, the banner video is playing. The video duration is variable. It can vary between 4-15 seconds. The user clicks the app to go inside, add items to the cart, and place the order. After the order is complete; it again redirects to the banner video screen. Problem: This process will keep happening all the day. The kiosk is never off. After 3-4 days when it's on its video gets paused; a blank screen shows and nothing happens. However, when the app is closed and reopened, it starts again. I have tried all the ways to find out why the screen goes blank and the video doesn't play. I have two kiosk machines with Android 9 and Android 13. Both have the same issue. These are MicroTouch's IC-series kiosks. Is it taking resources that get filled when used for a long time and filled? The player used by the dev is Exo Player. Is there any possible way to find out the exact reason why it's happening? I tried using it for a whole day. Kept it on for 2 days, but I didn't track the issue. We only face this issue at the user site where these kiosks are installed and when continuously used for 3 or 4 days.

I have this crap ANS ARTIA phone running Android 12. It keeps rebooting—2-3 times at the same date/time of the week (once while using G Maps, once using Waze) plus a couple more times outside of those circumstances. I'm broke and can't afford anything else, so I'm trying to fix it. One time it crashed to that dead android screen and the power button wouldn't even work. I had to do PWR+VOL UP like I was trying to get into fastboot just to reboot it. I saved 2 bug reports so far, one being quickly after a reboot. Online docs say to look for logcat.txt, but there isn't one in these reports, only dumpstate_log, main_entry, and version.txt in the parent folder, with several other folders. Someone said look for LAST KMSG, but the only mention of that is: > *** Error dumping /proc/last_kmsg (LAST KMSG): No such file or > directory ------ 0.001s was the duration of 'LAST KMSG' ------ I'll watch for it to happen again and try to capture another report immediately after, but I don't know how to recreate it on demand while plugged in to USB. I have ADB and Android Studio, but I don't know what to do with them. No results for am_anr. There are 4 files in \data\anr. No WATCHDOG KILLING, no am_focused_activity, > VM TRACES AT LAST ANR (/data/anr/anr_2023-06-08-16-07-26-347: > 2023-06-08 16:07:32) ------ > Subject: Input dispatching timed out (e036911 NavigationBar0 (server) is not responding. Waited 9633ms for MotionEvent) Someone said type *#9900# to turn on more verbose logging, but I get "invalid mmi code," and my carrier is a crappy free provider so that may never work. I got a bunch of am_proc_died at 17:39 and a bunch of am_proc_start around the same timestamp. I got 4 am_low_memory's but that was at a different timestamp. A few hits for kswapd, a ton of hits for kworker, but I don't know what I'm looking for. No hits for mmcqd. No Uncaught remote exceptions. > Line 11865: 12-31 18:00:15.858 1000 1644 1644 W PackageManager: > There should probably be exactly one storage manager; found 2: > matches=[ResolveInfo{5cce669 > com.google.android.apps.nbu.files/.home.HomeActivity p=100 > m=0x108000}, ResolveInfo{4a848ee > com.android.storagemanager/.deletionhelper.DeletionHelperActivity > m=0x108000}] Line 569647: 06-08 17:41:52.782 10221 15908 15908 E > HMSSDK_HMSPackageManager: resolveInfoList is null or empty Line > 569653: 06-08 17:41:52.789 10221 15908 15908 E > HMSSDK_HMSPackageManager: resolveInfoList is null or empty Line > 569657: 06-08 17:41:52.796 10221 15908 15908 E > HMSSDK_HMSPackageManager: resolveInfoList is null or empty > Line 27951: 06-08 17:42:58.876 1000 19810 19810 I > ResolverListAdapter: Add DisplayResolveInfo component: > ComponentInfo{com.google.android.apps.docs/com.google.android.apps.docs.common.shareitem.UploadMenuActivity}, > intent component: > ComponentInfo{com.google.android.apps.docs/com.google.android.apps.docs.common.shareitem.UploadMenuActivity} > > Line 27952: 06-08 17:42:58.877 1000 19810 19810 I > ResolverListAdapter: Add DisplayResolveInfo component: > ComponentInfo{com.google.android.gm/com.google.android.gm.ComposeActivityGmailExternal}, > intent component: > ComponentInfo{com.google.android.gm/com.google.android.gm.ComposeActivityGmailExternal} > > Line 28288: 06-08 17:43:06.745 1000 19810 19810 D ChooserActivity: > ResolveInfo Package is com.google.android.apps.docs > Line 34987: > 06-08 17:42:20.993 1000 1644 2177 I am_broadcast_discard_app: > [0,180397340,android.intent.action.MEDIA_MOUNTED,3,ResolveInfo{15d3531 > com.qti.ltebc/com.qualcomm.ltebc.LTEBroadcastReceiver m=0x208000}] > > Line 35064: 06-08 17:42:28.965 1000 1644 1902 I > am_broadcast_discard_app: > [0,65709818,android.intent.action.MEDIA_MOUNTED,3,ResolveInfo{7d87402 > com.qti.ltebc/com.qualcomm.ltebc.LTEBroadcastReceiver m=0x208000}] > > Line 35225: 06-08 17:42:49.671 1000 1644 2174 I > am_broadcast_discard_app: > [0,229308146,com.microsoft.bing.usbsdk.api.APPWIDGET_UPDATE,0,ResolveInfo{d90e5a1 > com.microsoft.bing/com.microsoft.clients.bing.widget.SearchBoxWidgetProvider > m=0x0}] Can someone please tell me why I don't have logcat or dumpsys? And can anyone tell me what to look for in these logs that might give me an idea of what is happening? Thanks!!!

I have a streaming app which has an internal player (not great) but it also allows us to use MX Player. The app is installed on my Android TV and also my Nvidia shield. On the android TV, if I chose to use the External player (MX Player) it works fine, MX player comes up and the stream plays there fine. On the shield, when I select to play on the External player, It opens the Play Store and a message pops up on the bottom of the screen asking me to install MX Player. However, MX player is already installed. I have tried uninstalling and reinstalling but it makes no difference. It is the exact same app on both devices and I can not understand why it works perfect on one but not the other. Are there any recommended areas to check?

When running adb devices in cmd, it says that my phone is unauthorized. It appears that it has something to do with the RSA fingerprint prompt. I don't remember ever getting such a prompt. Yes, I am running in PTP mode and debugging is enabled. I tried, after looking around on internet for multiple hours: * Enabling/disabling debugging mode repeatedly * Uninstalling and reinstalling my drivers for my phone or ADB * adb-killserver and adb-startserver * Restarting my phone and unplugging/replugging in multiple ways I did notice that in my (user)/.android/ folder, I don't have a file called adbkey.pub (which is apparently the file that's supposed to have my key). Anyway, I don't think I've ever received the prompt about RSA fingerprint and I can't make it appear in any way. Do you guys have any idea what I could do at this point. I tried about everything on these forums and around on the Internet but maybe there is something else I could do. Should I reset my phone to factory settings at this point to make the prompt appear again?

I've just come upon several .apk files hosted with Github projects which are "compiled for debug" (i.e. having application-debuggable set, which one can e.g. check using aapt dump badging /path/to/apk | grep debuggable. Not being an Android dev, I only have vague ideas what that is for (extended debugging via ADB) – but that's not the question here. **My question is from a *pure end-user perspective:* What are the (security) implications of installing/using such an app? What are the risks one must be aware of?** Of course I searched the web for hints on this, but again only got vague hints like "thou shalt not", and "for a release this should be switched off" – no reasons, no background. For that one could think "obviously no big deal" – but notes like *Do spend some time thinking about the security implications for your users* in this context (see [this answer](https://stackoverflow.com/a/15392081/2533433) at SO) suggest differently. Can anyone here provide some insights?

I had the following: on Firefox on Android, some links in a facebook post behaved this way: I got a pop-up window that there's no Internet and I should try again, and then the following screen appeared: How can I debug such a mishap, i.e. what happens here?

I found this project which allows me to connect to a WiFi through ADB commands not being a root user. I was wondering if anyone knows how to disconnect also from ADB and not being a root user. **UPDATE**: I've been recently trying: C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings adb server is out of date. killing... * daemon started successfully * Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings } Warning: Activity not started, its current task has been brought to the front and C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings } Warning: Activity not started, its current task has been brought to the front I also found doing this type of command: adb shell input keyevent 20 & adb shell input keyevent 23 I can navigate and click. The problem seems to be that I always finish in a different state so the next time I input the command adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings I start in a different place and start clicking elsewhere. I've tried returning home, but that doesn't fix the issue. Is there any way to start always from the same point inside the WiFi settings? Thanks!

I need to get dumpstate logs on a Samsung Fold device during device setup after first power on (after new binary flashing or factory reset). I am unable to set debug level high through *#9900# because the device is switching on for the first time. Is there a way to do this through adb? I have a custom ROM in which adb is pre-enabled. Thank you for your time 🙏🏼

Android 8.0.0: can not enable developer options for USB debugging? When I tap the "Developer Options", says: Turn on Developer options first. About Phone > Software Information > Build number. Tap the build number, says: Developer mode has already been turned on. Samsung Galaxy S7.

I would like to analyze deeply the behavior of the android permissions. When a permission is granted or not, what android do, etc. I have some ideas, but I would like to know which one could be the easiest one, or any new idea, or if some similar works have already been done. So I thought about: - frida - android studio using the debugging - making in local a java script using the same logic than in the aosp The logcat in Android Studio is very powerful, I can see the ActivityTaskManager and GrantPermissionsActivity for example. But I don't know what happened to call them, why these parameters etc. So, if you have any ideas, any tips, any documentations, I'm interested in. Thank you.

I got a system message that the keyboard had crashed. Then my keyboard won't restart. And now that my phone is locked, I can't unlock it to try any of the normal fixes, such has disabling and enabling the keyboard. Yes, I have restarted the phone, that's why it's locked now. I need to save some of the contacts, so a simple factory reset won't work. ADB does seem to be enabled, but I don't know how export the contacts, or install a keyboard. How can I either restore the keyboard, or export the contacts.

so far I have put my android device in ftm mode i have tried from adb sideload now i am trying with busybox ash I'm able to run ls but anything else says permission denied or error:closed. / $ ls acct cache charger config d data default.prop dev etc file_contexts firmware fstab.qcom icon_ftm.png init init.class_main.sh init.environ.rc init.ftm.rc init.mdm.sh init.offcharge.rc init.qcom.bms.sh init.qcom.class_core.sh init.qcom.early_boot.sh init.qcom.factory.rc init.qcom.ftm.rc init.qcom.rc init.qcom.sh init.qcom.syspart_fixup.sh init.qcom.usb.rc init.qcom.usb.sh init.rc init.target.ftm.rc init.target.rc init.trace.rc init.usb.rc init.vendor.rc init.zygote32.rc mnt persist proc property_contexts res root sbin sdcard seapp_contexts selinux_version sepolicy service_contexts storage sys system tombstones ueventd.qcom.rc ueventd.rc vendor verity_key

My sister's Nexus 5X won't turn on. It is charged. When you try to power on, it makes it to the Google animation but freezes and goes back to black. You can make it to the debug menu go through the options, but when you choose Start it does the same thing. We've tried the Google Support suggestions, and nothing is working.

If I have bug reports enabled in dev options and I take a bugreport from the power button menu, where are these reports saved? I see there is an option to share it, but I want to pull it directly through adb for analysis.

I search hours on internet but didn't find solution. I install Android x86 and Android Phoenix OS on VMware Workstation. Both Freezing in x86_64:/ # and Android doesn't come up But I Found Solution and it's Work. editt kernel and add this "nomodeset xforcevesa" Now Problem is: in Android x86 in grub menu it has debug mode and I can choose it and go through editing But in Android Phoenix OS there is no debug mode in menu. So How I Access to Debug mode in Phoenix OS? is has any command that i use in CLT to run debug mode? Please see the images below:

I am starting Android development, and I am looking for a way to get a bug report from a user's phone. I know about the Settings / Developer options / Take bug report system, but from what I have seen, it dumps *all* logs from all sorts of apps I don't really care about. Is there a similar method which would generate a similar file, with just logs relevant to my app? (I also know about adb logcat, which I can then filter on my computer during development, but it's not easy asking users to do that!)