I have a boot looping Samsung Galaxy S4 Mini LTE (also known as GT-i9195 or serranoltexx – this is not GT-i9195i or serranoveltexx). **Current behavior:** when the phone is off, pressing power button results to normal boot screen with usual yellow text in the top left corner about custom kernel ("Set Warranty Bit : kernel"). The screen stays in this view for around 20 seconds, turns to black, vibration motor runs for two short periods and the system reboots. I guess the system is failing to boot until hardware watchdog resets the system due timeout exeeding. If I boot with Volume down + Home + Power held, the phone enters into download mode as usual. And if I boot with Volume up + Home + Power held, the phone enters recovery mode (TWRP version 3.3.1.0) where everything seems to work as usual, too. I was running LineageOS 16 (Android 9.0) with SELinux enforcement enabled with June 2019 security patches. The system has XXUCOL3 modem firmware if I remember correctly. In the end, I can successfully boot into download mode and into TWRP recovery. However, the system started to fail to boot to normal system after normal shutdown-restart cycle and the system was working okay before shutdown. **Is there any way to diagnose and possibly fix the problem without wiping all the data?** Steps that I've already tried: - Wiping Art/Dalwik Cache, Cache partition and System partition and re-installing full system image via TWRP. - Removing battery - Booting with SIM card and sdcard removed I really want to understand why this happened to avoid it in the future. I really don't want to have a device that randomly enters this state and the only way to fix it is to wipe the whole device. Being able to bring the current system to usable state without full wipe would be a nice bonus because it avoids reconfiguring all the settings and apps again. And yes, I know this device is old and I had to previously replace motherboard due emmc chip failing but I really like the form factor and no vendor is nowadays providing similar device. If Sharp Aquos R2 compact didn't have notches on the screen it would be my next phone.

How do I access the diag screen programmatically on a Honda Clarity 2018 PHEV non-touring (with root)? Clarity's has a damaged HMU (touch digitizer not functioning). I have root on the unit, and USB/wireless debugging is enabled, so I am still able to operate the head unit (through ADB shell, or somewhat through the frontend by sending emulated input keyevent or other key events). However, this leaves the touch keys on the side of the screen inoperable, as they are not (to my inference, thus far) considered virtual navigation keys, but rather appear to be additional hardware input device keys. I've checked the listed key codes within system/usr/keychars and system/usr/keymaps, but sending these through ADB doesn't appear to do anything. Furthermore, even if I am able to find the correct input keyevent codes, I'm not certain it will be possible to invoke the Audio+Menu+Brightness keys together, and whether doing so would work to invoke the diag menu? I've also thought to directly call systemdiag through adb shell start, but none of the activity URI's enumerated via systemdump appear to be accepted, and all result in component name errors. I'm sure this should also be possible, but I'm not sure whether I'm committing a syntactical error or just using the incorrect activities altogether.

A family member's OnePlus 7T (latest factory firmware) keeps trying to sporadically but frequently ARP spoof the local default gw address on our wifi. Is there a way, perhaps involving adb, that would help me find the app or process responsible? (I'm fairly certain it's the phone, and not some device that tries to implicate the phone, because it only happens when the phone is actually around.)

I have One Plus Nord device which is rooted using Magisk. I am able to enable the usb tethering(rndis) and capturing modem logs(diag) separately using the libusb program. But the requirement is to capture the diag logs when the phone is connected with laptop and usb tethering is enabled. Following are the commands used to enable the ports: 1. To enable "Usb Tethering" adb shell su -c "setprop sys.usb.config rndis,none,adb" 2. To enable the "Diag" adb shell su -c "setprop sys.usb.config diag,adb" I have tried to enable both using different set of commands like - adb shell su -c "setprop sys.usb.config rndis,diag,adb" - adb shell su -c "setprop sys.usb.config rndis,none,diag,adb" - adb shell su -c "setprop sys.usb.config diag,rndis,adb" etc.. bot none is working. Does anyone have knowledge of how to use both together or any hint which can help in achieving the goal?

I have a very annoying problem with my phone's Google Apps, which I cannot resolve or even diagnose. It affects Google Play, Google Maps, Chrome, YouYube, Google Settings, Account managing, and probably other apps. All of these freeze when I try to access them and after a while the message "(App) isn't responding" appears. Interestingly, the Google app (the search engine), the Gmail app, and Google Translate function properly. At first, I though I got a virus or some new update caused the problem, so I cleared the data of Google Play and restarted the phone. Unfortunately, for no avail. Next, I thought it's an Internet connection problem, however, other apps which need web access work fine (e.g. Evernote, Duolingo, a racing game /Top Drives/ that I play from time to time, and even my secondary browser /UC Browser/). For this reason, I took drastic measures and reset my phone to its factory settings (without restoring any previous data). Again - nothing. On top of everything, my battery suddenly started draining away faster than usual and I suspect Google Play services to be the cause of that. When I checked my Battery history, I saw that even under idle mode, Google Play is using CPU for something. I should point that after I reset the phone, I entered *play.google.com* from my other browser and noticed that the site still thought that my old apps (the ones which I used to have before formatting my phone) were still installed on my device. Clearly, this means that Google Play and my phone don't synchronize properly. At this stage, I'm left in the dark. I have no idea if the problem is software, hardware, or authorization related. I should point out that I borrowed an old smartphone from a friend of mine and was able to load a functional android configuration on it with my Gmail. Does anyone know what may be the cause of this issue or who has experiences something similar? I already read all standard solutions listed on the Google Support forum and none of them worked. PS My phone is Lenovo P1 Vibe, less then 2 years old. My Android version is 5.1. Last time I could use the phone normally was 2 days ago, when I watched a show on the Internet before going to bed. I noticed the problem after I charged it the next morning.

I'm trying to diagnose a random reboot on LineageOS 14. last_kmsg is not in /proc, nor it is in /sys/fs/pstore/console-ramoops. **EDIT:** ~# mount | grep PSTORE ~# mkdir /mnt/pstore && mount pstore -t pstore /mnt/pstore && ls /mnt/pstore mount: 'pstore'->'/mnt/pstore': No such device

Under battery usage, I can see “battery usage since full charge,” broken down by app (and, if toggled on, non-app phone processes). I’d like to see that breakdown but in a more specific timeframe (and, if possible, prior to my last full charge). The phone is a Motorola “moto g power” running Android version 11, security update June 1, 2021. ### Context: Last night, I went to bed with my phone at 49% (I checked because had been a bit since I charged it); this morning it was dead. The battery usage graph showed four days of steadily-declining battery, to just under 50% as I saw it last night, followed by a nose-dive to 0% in a few hours. The breakdown of usage showed about a third used by Firefox (makes sense, that’s the overwhelming majority of my usage of the phone), about a third used by “mobile network standby” (which makes little sense, I have pretty good signal), and the rest divided among a bunch of different things. My assumption is that Firefox was the dominant usage over most of those four days, and mobile network standby is what caused the precipitous drop last night. However, I don’t *know* that—it could be that mobile network standby is always draining my battery more than I think it is, and something *else* (probably increased usage by Firefox?) last night caused the drain. ### Question: Is there any way to get that same battery usage breakdown, but for just those hours last night, rather than “since last full charge”? For that matter, I have since charged the phone, so now it displays no data since it just charged—is the record I described above just gone now?

I've been wondering a lot about this when it happened which I was using Walli* app yet after I have changed my ROM, maybe the app gets blank no matter how I install it. But after a time, I've also realized that there is another app called Reface with the same problem in which I can't use them because they're blank like there is no connection to the Internet. Note: I'm using **Cloudflare Family DNS** on my router and Firewall settings such **SPI** and **DOS protection**. My ROM: AOSP based 7.1.2 Android custom ROM

I connected an Android phone to a vehicle via bluetooth to make/receive calls. Connecting the device via bluetooth was simple. Making calls, however, was a challenge. The vehicle reports that the Android phone is always without cell reception, and therefore will not place calls. Furthermore, the vehicle's *head unit* (aka *receiver*) shows a "no reception" indicator for the Android device's cell reception. Placing calls **from the Android device** through the vehicle's audio system works as expected. This also shows that the Android device has ample cell reception to make calls. **What techniques or apps can be used to diagnose what is going wrong?** Ideally, I would like to see what the Android device is transmitting to the vehicle that is causing the vehicle to think the Android device has no reception. For example, an app that simulates a vehicle's *head unit* (perhaps with added diagnostics) would be useful.

The ADB method is easy enough, but I may not have a computer at hand. Can I retrieve the PID with a Termux package or an app, or any other methods (including those which require root)?

In my Android settings (Version 6) I have the option to activate "to automatically share usage and diagnostics data". I suppose that this will help certain developpers - and of course Google - by getting statistics of my battery states and usage (as the title says). But appart from getting "more wonderful and stable apps" in later versions, is there any specific advantage for me? I am asking this as a user and as a developper (who has noticed that many users have this option turned off). In our part of the world (Africa) we are still paying for data, so providing this information will cost me and other users real money. Do you know about any more direct incentive? Like "better status" in the Play Store? Brownie Points with Google? Or - at least - **can I have access somewhere and see what Google is collecting about my own usage and my own battery performance**? That would be an incentive indeed. I might find that I spend much more time with my phone than I think (or maybe that way I discover that my baboon is using it when I leave the room...). Please do not hate this question; I have started investigating this subject today, because some of our apps have just started giving crash-reports on the Play Console, so am collecting any information I can - from the dev-side and from the users-side. Thank you. Edit: Since the first answer is questioning my mention of battery-information in my initial question, I will paste here a short summary from a Google Android Account Help page which does mention battery-level: > **What information is shared with Google** If you turn on usage and > diagnostics, your device sends information to Google about what’s > working and not working. For example, your device can send information > like battery level, how often you use your apps, and the quality and > length of your network connections (like mobile, Wi-Fi, and > Bluetooth). None of this information is used to identify you.

My LG G4's notification LED has started intermittently flashing yellow for unknown reasons. Normally, I would assume that a notification is causing it, but in this case, no notifications are present and clearing the existing ones doesn't stop the flashing. I have not (knowingly) set an app to flash either. Is there a way to diagnose which app is causing the flashing?

Okay here is what happened Yesterday I restrated my phone beacuse the volume and power keys were acting funny but instead of booting into the system in boots into TWRP btw just in case I installed a custom rom before i restarted this okay back to the problem today I gave up trying to flash new custom roms since It keeps booting into TWRP so i decided to go with the stock rom I flashed with Miflash hoping it would fix but now TWRP is gone can't turn off my phone,can't boot into fastboot or bootloader,all I can is Mi-Recovery 3.0 also just to add my volume up key wont work that's the reason for why i think there is damage on my volume up key. From the Main Menu of Mi-Recovery 3.0 all i could do is reboot to system which just makes it boot bact to recovery and wipe data which also did'nt work, Connect with MIAssistant is also useless since the app cant detect it. Thats all.

I suspect the Internal Storage on my device is failing. How can I confirm? If this were a computer, I would check the S.M.A.R.T. data for each storage device. I am looking for something similar. Misc: - My device was released over three years ago. I'm running a Marshmallow, custom stock ROM, rooted with Magisk, and with Xposed installed. - I recently wiped my device and reinstalled the custom ROM. - When requesting root, MagiskManager often crashes and logcat reports: android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 1034) - I occasionally see other I/O error messages fly by on logcat - From recovery, the e2fsck / fsck.f2fs commands report no filesystem errors.

I dropped my Pixel. The screen is cracked and doesn't light up. But the phone still works - it rings and vibrates when I get a call. I'm considering replacing the screen myself, but before I buy the part, I'm wondering if there is any way to have confidence that the screen is the only problem. Can I connect my phone to the computer via USB, and then run some kind of diagnostic software from the computer, to tell me exactly which parts are damaged besides the screen (if any)?

My Sony Xperia M5 is not booting up. The screen is off, no LEDs are lit, it doesn't react to any buttons. It already happened several times. I wasn't doing anything specific, just was using it normally, and then suddenly it would hang up. This last time it happened while it was charging. 1. After about 9 months of usage, it went into a boot loop, which I was able to resolve by switching it off/on (with a hidden power button). It took several attempts, though. 2. About 2 or 3 weeks later, it went into a boot loop again. This time switching it off didn't help, so I tried resetting the firmware using the official tool from Sony. It didn't help either, so I brought it to the after sales service. They updated the firmware, and it was enough to fix it. They wrote that "the defect was not found" in their report. 3. After 2 or 3 weeks, the phone stopped working at all: the screen is off, not responding to any buttons, including hidden power button and combos like power+volume up/down. Again, brought it to the service, with the same result: resetting firmware helped, but "the defect was not found". This time they did some "WRT test" (no one has any idea what it is exactly), which was fine too. 4. Now, again, after 2 or 3 weeks, same happened - not working at all. Phone condition is fine and I used it properly: - It hasn't fallen once, didn't contact any water, was not affected by extreme temperatures, (electro-)magnetic fields, radiation, etc. - Viruses are pretty much excluded: it had an antivirus installed, I only used apps from Google Play, and only the ones I trusted. I don't use any Wi-Fi spots outside of my home and office. - The battery is fine. Now, I just want my money back, but the only two documents I have on hand say that the device is perfectly fine, so the shop will refuse it. I want something to prove the defect is actually there. My questions are: - **What kind of problem can it be?** If it's a hardware problem, why would firmware reset fix it? If it's a software problem, why would it even occur? My only idea is that it's a memory failure, but there was no indication of that when I did the firmware reset (I assume it should do at least basic tests). - **Is there a way to perform any conclusive tests by myself?** I talked to managers in the service center, and they pretty much don't care. I have to chance to talk to engineers directly. I won't open the case or anything like that, and also now it's doesn't load at all, so the only options is to use some software on PC, with a USB cable. Is there any software for that?