Hoping someone knows how to do this...
I have recurring reboots when I use google maps navigation, and I am trying to narrow the problem down to hardware or software. I am trying to use adb to capture the event in a log, but there is a buffer (delay) between the events on the phone and them showing up in the log on my PC screen. So when my phone spontaneously reboots, I don't see anything in the log that is causing it. I'm guessing it just doesn't have time to get it out of the buffer before the reboot. Of course, upon reboot, the log is cleared and I can't see anything.
Does anyone know of an adb logcat option or an entirely different approach that will eliminate this buffer and give me real-time activity monitoring so I can see the reboot in the log? Any other way to solve this problem??
Related
Summary
Immediately after reboot, the time it takes to get a GPS fix will be much longer. Take the following two test cases I have tried:
1. Reboot. Then immediately open GPS Status. It will take 90-120 seconds to get a fix.
2. Reboot. Wait at least 3 minutes. Then open GPS Status. It will take about 12-18 seconds to get a fix. (In case anyone is wondering, there isn't anything running in the background that is getting a fix while I'm waiting.)
I found this out by accident. I was playing around with various gps.conf files, which requires a reboot every time you modify it. No matter what I put in that file it would take much too long to get a fix. But after running a few tests, I did determine that you need to wait at least a few minutes after rebooting to test.
Repro Steps
Here are instructions to find out whether you will encounter this same issue:
Put on a gps.conf file that has INTERMEDIATE_POS=1 (not required, but recommended: will be explained below). You can use the 3.1 / 2.2 no SSL version from this post by @crypted.
Make sure gps.conf has read permissions for all of owner/group/other (not related to this issue specifically, but just a general note to make sure gps.conf is being read correctly).
Install GPS Status, and make sure the following option is checked: Settings > Display & Tools > Show time to GPS fix.
Reboot the phone.
Start GPS Status immediately. Take note of whether you get the message "Time to first GPS fix: 2s" (see my screenshot). If you see this message, then you should get the fix within a few seconds when you are outside. If you don't, it will take a long time to get a fix. In this case, stop GPS status, wait 3 minutes and try again.
Note: If you don't have INTERMEDIATE_POS=1, you will still get the same behaviour except you will not get the "Time to first GPS fix" message until you actually get a fix, so you will just have to wait a few minutes. You can use 'uptime' in a terminal and once it shows 3 minutes then you should be able to get a quick fix.
Cause
I have no idea why this happens. I'm guessing that for some reason the GPS driver will not use the AGPS data until after a few minutes after bootup. This is speculation though. If anyone with more knowledge has any insight, please share.
Conclusion
I have no solution to get around this. But hopefully this will help explain why you may not get a fast GPS fix at times. This is not really a big issue for regular users as they're not constantly rebooting. This is more important to consider if you are benchmarking various gps.conf configurations.
I'd be interested to know if anyone else is seeing something similar. I have no idea if this is specific to T999, Cyanogenmod, Qualcomm chips, or just me.
Here's an odd one. Maybe my search terms are iffy, but I can't find anyone else with this issue.
When I uninstall the app on my phone for a watch face, Android will often (almost always) crash when that app/face gets uninstalled from the watch.
I say "Android" because the watch itself doesn't crash and reboot, but Android restarts (ie back to the boot-animation but not back to the bootloader).
I'll try and reproduce this with adb connected and see if I can glean some logs... that'll likely clear it up for me, but I'll post my findings here in case someone else has the same problem.
I've noticed similar behaviour also, but only if im currently using that watch face and then uninstall it from the phone. If i switch to another one beforehand, nothing happens.
It also seems to happen with other apps, though I can't see a similar pattern there, it happens whether or not I'm using it, and often not at all.
Starting early July, my Pixel 2 XL on stock Google ROM has been crashing constantly. Tried a whole sort of troubleshooting but cant seem to fix it. Looking to see if someone can see something that I dont.
Symptoms
When Pixel 2 XL, on (PQ3A.190705.001, Jul 2019), charging and left alone, the phone would become unresponsive for up to 5 minutes, then proceed to do a soft restart and show the Phone is initializing. No problems when running the phone off the charger.
Troubleshooting
Tried the basic troubleshooting steps from Google Support (Update to latest system update, remove free space, safe mode, factory reset)
Tried reflash June factory image from Google (PQ3A.190605.003, Jun 2019)
Tried different charger
Disabled digital wellness app
Disabled the Private DNS and uninstalled Blockada (heard issues with it)
Nothing seems to work. Google support suggested that I get it exchanged under warranty, however, I feel like it is a software issue more than hardware. This is because when I monitor it under logcat when it stops responding, I see there is a whole bunch uncaught FATAL EXCEPTION so it seems that something is causing it to error out.
I am not too familiar with Android logs so I cant pinpoint it out. If anyone have more expertise can help with taking a look at the log to see what the root cause is, that would let me know what I should do for next step (ie try Android Q Beta if it is a system issue, get a new phone if it is a HW issue, or change certain settings).
Here is the log file
Thanks
Today I experienced my first "random" reboot since I owned this phone.
Came home from work, checked the notifications on the device and saw I have 2 app updates I have to make: Google calendar and Facebook messenger. Let play store update the apps and opened them, but when I opened Google Calendar, the screen went black and then it started to roll that color line and I was back on the lock screen. This is the first time something like this happened, so is there a way to check and see what went wrong and what was the cause of that system crash? Also is there a way to reflash via recovery 11.0.7 if I'm already on 11.0.7?
adb logcat from a PC (redirect to a file).
Mattlog or similar from the device.
The logcat is not very big. Capture it quick or you'll lose it.
HI,
My GWA 2 is getting rebooted randomly, I was able to collect dump logs , copied it on computer and can see @@@@@@ characters in kernel log around crash time, no other alarms in logs, After enabling debug mode, On crashing now watch goes into a screen with watchdog logo in background and some watch details on top, but no touch/button works to see rest of the logs. I am able to pass all the test in test mode. I have reset watch multiple times. Can some tizen developer help me in debugging, What other steps I can do to easily diagnose the issue? Can I get the backtrace of the OS crash?