Occasionally (maybe twice a month) my **Milestone** just reboots (goes black and then to the Android start-up screen, but not all the way to the Motorola screen). I presume that such behaviour could be caused a poorly written app. I have uninstalled a few but to no avail. Is there any sort of log that I could pull which would shed some light on this or even a dump file? Could this restarting issue be caused by something else? I am currently running **Android 2.1** (no OTA update available for me, yet) on a Milestone and have had this problem since I bought it in December (when it was 2.0).

I need to force a selected application to start up each time my Android-based device is (re)started. Is there anything I can use (configuration setting, external application etc.) to accomplish this task? Or is this kind of behavior limited to home screen managers only?

When freezing apps using Titanium Backup Pro, do I have to reboot for the freeze to take effect? (e.g. not be started anymore, even if applicaple Intent is fired off?) Does it depend on whether the app is a system one or not? If it matters, environment is Droid X (Stock 2.2 Froyo, rooted), latest Market version of TBPro. I tried checking on TB Wiki and found zero reference to rebooting or not as far as freezing functionality. -------------------- Here's a specific example: consider the following sequence: 1. "GPS location changed" intent fires off. 2. A mapping application "MyGMaps" which is registered for this intent is started to handle it 3. I kill that application's process(es) - all of them - via Advanced Task Killer 4. I freeze "MyGMaps" via Titanium Backup Pro 5. At this point, "MyGMaps" process is NOT running 6. "GPS location changed" intent fires off again 7. What happens here? Will "MyGMaps" be started again due to the intent in #6, despite the fact that it's "Frozen"? My understanding is that, once I reboot the phone after freezing, the app will no longer start at all. **But what happens in step #7, right after the freeze but without a reboot?**

My Motorola One Hyper phone starts, finishes the boot animation, then I unlock it with the PIN number, then it opens and there is the problem. It stays on for about 5 to 10 seconds where I can use it, and then a black screen covers whatever I'm doing that says it is resetting to factory reset and restarting. It loads for a few seconds and reboots. When it starts, it goes directly to recover where it shows me only two options. 1) Restart 2) Factory reset I need to access the data on the phone before I can factory reset. I don't care about saving the current installation, but before resetting, I need to extract my data. I would like to be able to explore the phone before a factory reset. I can use the phone "normally" for those few seconds it turns on, I can access menus and enable or disable options (I could manage to enter developer mode). I tried safe mode but it is the same. I tried the Rescue and Smart Assistant tool, but it also requires the phone to be on the main screen and with the app opened and that is precisely my issue. Any input or suggestion on how to access the data or what to try would be appreciated. Since I don't know if the device is rooted nor I have done anything of the sort, I assume it is not. Maybe even a process I can stop or something to just be able to keep the phone on enough to browse the files and then factory reset or reinstall or update firmware.

I recently got a new phone, a Landvo XM100 Plus. It sometimes reboots randomly which doesn't bother me much, but what's annoying is that it keeps setting the system language to German. I did not have these issues on my old phone (Samsung Galaxy S3), and I don't have the problem when there is no SIM Card inserted. However, I'm using the same SIM that I used in my old phone, so I'm really confused as to what is going on. I tried googling the issue and I ended up at a few different boards with everyone basically scratching their heads. Could it be the custom ROM the manufacturer uses? I don't quite want to flash my phone with a different OS right now since I still got a warranty. Any ideas?

I'm trying to have my Samsung Galaxy S7 phone start up into normal operation when USB power comes on. I have tested all the suggestions in [this post](https://stackoverflow.com/questions/4169387/how-to-make-android-device-boot-when-power-is-plugged-in) and several others, but whatever I do the phone will not reboot into normal operation. My result is no reboot or reboot into Recovery mode. I have also tested several ROMs with same result. There seems to be a problem when the \system\bin\reboot is called in LPM (Low Power Mode) mode. Script: #!/system/bin/sh /system/bin/lpm_orig & while [ true ]; do sleep 1 ps | grep lpm_orig && sleep 3 && /system/bin/reboot done (The "lpm_orig" is the original lpm file). Linux owner and execution rights have been checked. Does anyone have an idea what to try next?

After recording with Field Recorder , I connect my Lenovo S6000L via USB to my PC. However, the newly recorded audio files in WAV format are not visible until I reboot the tablet. Android version is 4.2.2. *Is that likely an OS or an app issue? Can I avoid the lengthy reboot?*

I recently bought a refurbished Google Pixel 8 which was clearly unusable: The phone rebooted each time I used a feature which was consuming some power (Start to view a video on youtube, Take a picture using the camera, Starting some apps, calling someone ...) These "reboots" are different from reboots using the power button: The screen becomes black during a few seconds then the welcome screen is displayed again. There is no android nor google logo displayed before the welcome screen. I applied all OS and apps updates and the problem was still there. I started to debug the phone using logcat feature of Android Studio to see if there is some interesting information printed before such restart. I did not do anything else and the problem disappeared ! I disabled the developer mode required to debug using Android Studio and the issue did NOT reappear. What is the cause of these restarts ? How Android Studio debugging can fix such issue ?

I just recently had an issue with my phone. It's a Samsung Galaxy A51 (not the 5G, SM-A515U) from Xfinity Mobile (Android 13). Unfortunately, the screen is cracked. It still was functioning properly until now. It has not been rooted. I earlier this year had the issue with the grey ring and lightning bolt, but I solved that with some help from Redditors. Nonetheless, the problem never went away; I was using the phone as I normally do and it suddenly froze, so I hooked it up to my computer and used the ADB to reboot. It won't turn back on. When I repeatedly tap the power button, the phone vibrates and an alarm sounds. When I hold the Power key to turn it on, the phone vibrates, but the screen is blank. I can see the phone in my Device Manager and the ADB on my computer, but it doesn't show up in Windows Explorer (Windows 11 23H2). I can't even boot into Recovery mode. I could really use some help, as I've no money to fix my phone and it's the only one I have.

So i'm having this really baffling issue. I was using CM13 before and now using CM12 and both of them are facing the same issue. I am using Galaxy Mega i9152. There are certain applications, that have been causing my phone to reboot upon install or launch. Previously, it was Yahoo Mail (which i have not used since), then it was some other games (names of which i don't remember) and now it is WhatsApp messenger. I thought the problem was with the CM13 rom, so i did a clean flash ( wiped data, cache, basically everything other than internal/external storage) of CM12 (hoping to get the 'move to SD card' feature as a bonus). But, it did not resolve the issue. I just tried to install WhatsApp on my new ROM and it restarted as soon as WhatsApp finished Installing. This has me thinking that the issue is not with Apps, but something to do with a deeper level. I'm not an expert in Kernels or such. So please, can someone help me out here? Any insight i can get into the issue ? WhatsApp is really important for managing day-to-day affairs, so please help me out.

I've OnePlus 9 Pro with Android 13. The phone is rooted and has a custom ROM, but my issue isn't common for that ROM. The Phone generally works well, however at least once or twice a day it suffers random reboots. Sometimes it's during a call, sometimes when browsing the internet, and sometimes I spot the phone rebooting while lying on the desk, so the issue is not related to a particular task. I haven't updated my ROM for a while, I'll do it today, however, the problem did persist through updates earlier. It has that annoying habit since I've installed crDroid, it didn't have so on stock rooted firmware. I've flashed it strictly by the manual of ROM developers - from stock firmware to crDroid, all updates were installed after upgrading firmware, as it was mentioned by the devs of ROM, so I think that it must be one of randomly crashing apps. I know about logcat, but it definitely has too many lines to find anything out of it (another thing that I'm not sure about is if it persists through a reboot). So, I was wondering, if it's possible, how to find out a particular reason for such a random reboot. Is there any event log in Android, or someone could recommend such an app? Is there any other source of knowledge in Android or a Magisk module to log such things?

I own a Galaxy Tab Pro 8.4 Wifi (SM-T320), with LineageOS 20 (Android 13). I always had a weird behaviour with this tablet. When the tablet battery value is between 25% to 29%, the screen flicker, and it shuts down, Then, it reboots loop. If I plug in my charger, the battery value is equal to the value before it reboots loop. If if do nothing, it reboots loop until it stops, and the battery value is lower than 5%. The weird thing is that when I reboot to TWRP, the battery value is equal to the value before the reboot loop process, and if I let the tablet with TWRP open, it stays in power for more than a hour, with the screen brightness to max. So the battery health is not the issue here. I tried the calibration process (recharge to 100%, drain the battery, go to TWRP and delete batterystats.bin, than reboot), but the issue is still here. How can I fix that?

When I turn off my phone, next time it says SD card is damaged and all data is gone, I can only reformat it. The phone is "gionee iq275" (also known as "Fly" in Russia), Android version is 2.3.4. What can be the source of problem? How can I get rid of it? I know, the phone is crap, but at the moment just throwing it away and buying another is not a solution.

My Samsung Galaxy S10e restarts when I turn on the hotspot. I have checked for updates but they are not available. How can I fix it?

I updated my Samsung Galaxy A51 to Android 13 (One UI 5.1). My phone screen keeps freezing, going black, and restarting on its own. It happens every couple of minutes. I did almost every possible way I searched online like hard reset and all settings reset. Memory is not full. How can I fix it?

I often end up accidentally rebooting my Nexus 6 while having it in my pocket, because the power buttons gets pushed for more than 10 seconds. Considering the long boot times, this can be very annoying. I can see why it is important to have a way to force-reboot your when it gets stuck, even though I haven't had this type of issue yet. Is there are way I can change the force-reboot behaviour? Perhaps increase the time in which power button must be pushed or change it to a combination of buttons (i.e. volume up + power button for 10 seconds) ...anythign that makes it less likely to be triggered by my pocket.

Power button broke months ago. I've been very careful to never let it shut off, but last night it finally happened. Is there any way to make it reboot? I tried pressing Volume- and plugging in, and that brought up the boot menu, but you need to use the power button to select anything from the boot menu so now I'm stuck. In fact, I may be worse off because now I'm stuck in the boot menu. I tried adb restart, but adb doesn't see the device. (It can see other Android devices, so I know adb is installed and functioning.)

The long press on the Power button that I used on my earlier Android (Oreo) is now popping up the assistant. So what is the secret gesture? This is for a Pixel 7 if that makes a difference.

I am currently facing an issue with my Samsung Galaxy Tab 2 tablet running Lineage OS. Whenever I attempt to reboot the device using the adb reboot command through adb, it enters a strange hanging state - the screen turns off, and it becomes unresponsive to any further commands. It remains in this state until I physically unplug the USB cable, at which point the tablet restarts and functions normally again. Interestingly, during this state, the adb daemon fails to recognize the device, but lsusb still detects its presence. I have attempted to restart the USB port/device using usbreset,

sudo usbreset 18d1:4ee7

but within the dmesg log, I get attempts with several errors saying usb 1-1: device descriptor read/64, error -71 followed by finally with usb usb1-port1: attempt power cycle (full error output [here](https://pastebin.com/E4PpBNgb)) . The terminal output is

Resetting Galaxy Tab 2 ... failed [No such device]

And the computer (in my case, a Raspberry Pi Zero W) does not recognize the Android device anymore until I disconnect the USB. I have tried restarting the RPi but still no luck, since I assume a complete "power cycle" would trigger it since it only operates after disconnection or reset of the 5V connection in the USB. One hacky solution I have contemplating was creating a switch with the GPIO pins as a variant from this [post](https://electronics.stackexchange.com/q/104564/347607) , but I am still optimistic for a software-only solution before I start throwing hardware into the mix. Here are some additional details that might be useful:

Tablet model: Samsung Galaxy Tab 2

adb shell getprop ro.build.version.release: 7.1.2
adb shell getprop ro.build.version.sdk: 25
adb shell getprop ro.build.flavor: lineage_espressowifi-userdebug
adb shell getprop ro.build.description:
espresso10wifixx-user 4.2.2 JDQ39 P5110XXDML1 release-keys

$adb --version
Android Debug Bridge version 1.0.41
Version 28.0.2-debian
Installed as /usr/lib/android-sdk/platform-tools/adb

Any suggestions are appreciated!

When writing: adb reboot -p I expect the unit to power down indefinitely. Instead, it just reboots automatically, the same as having written: adb reboot only. Why is that? What should I write?