(Searches haven't turned up anything good yet)
I am experiencing a couple of hard crashes (with DC2.07.2, but that is irrelevent) and I am trying to figure out how to use logcat to determine what is causing the reboots.
Other than typing "adb logcat -f /sdcard/logfile.txt" or downloading the Log Collector from the market, does anyone have any tips or a guide for filtering the logs and tracking such a thing down?
What sort of red flags should I be looking for in the logs?
Are there any root apps that can read the logs directly? It seems I am never near a computer with the SDK installed when crashes occur.
thanks!
Related
Hey Guys,
Over the last few days my charge has rebooted a few times on me, its not a full reboot it’s a hot reboot. Here are the logs
I have not been near a computer with adb installed when these happen so I was not able to get logs from adb.
Ideas?
I'm no pro at reading log files, but I do notice a paypal nullpointerexception and what appears to be a DB issue that starts here:
W/SQLiteCompiledSql( 6270): at com.android.providers.contacts.MakeSimDBService.run(MakeSimDBService.java:326)
Are you using stock OTA? Third party contacts program?
Stock OTA and no 3rd party contact programs
I didn't see any problems either, but it looks like the logs were truncated at some point (beginning and/or end) of the files.
Hi,
I use Tiamat 2.2.2 on a Wifi Xoom and noticed that I cannot send emails from the built-in email app. The messages I am trying to send are always stored in the draft folder.
Logcat tells me that sending emails in inhibited while a monkey is using the device.
So I decompiled the email app and as it turns out there is a check for the monkey test driver that cause the email not to be sent when ActivityManager.isUserAMonkey returns true.
Now, that method usually read the ro-monkey system property and if it is set to 1 / true will return true.
To check I also called the isUserAMonkey method from one of my own apps and it returns true for sure.
The questions is why. getprop will not show the ro.monkey system property set. When I set it using setprop ro.monkey 0 the method still returns true.
Now I wonder if there is something deep inside the system property implementation that was changed to always return true for some reason. I could not find anything until now.
The ActivityManager.isUserAMonkey method looks normal to me after decompilation. So if there is a patche somewhere it's got to be deeper (maybe on the native level).
I searched for this porblem but was unable to find a similar report of this issue which I find quite strange as sending email should be a common use case.
I'm stuck at this point and would appreciate some help with this.
Thanks, Thomas
POTENTIAL FIX: PLEASE SEE UPDATE 2 BELOW!!!
Hey everyone, got a really odd issue and I seem to not be the only one.
I decided to get back into some Android development now that I have a bit of free time.
Went through the whole process of installing Android Studio, SDK, etc, etc without any problems. Decided to also get my OPO connected because I'd rather test on a physical device.
HOWEVER, I had logcat running and kept noticing my device would just randomly "disconnect" for no apparent reason. I phrase "disconnect" like that because ADB would just say the device is "offline" but still connected, despite being unlocked and very much on.
So I'd see something like this:
Code:
List of devices attached
XXXXXXX device
And then maybe a minute or two (random) later:
Code:
List of devices attached
XXXXXXX offline
I'm on stock CM12 (YNG1TAS213) and Windows 8.1 (64bit). I'm using the Google USB Drivers.
I've tested this on two machines (albeit, both 8.1). Additionally, it seems others are having the issues regardless of the OS (I can't post links b/c I'm a new member but there are two threads on the OPO forums with this issue).
I do have a 2012 Nexus 7 so I'll attempt to see if I'm getting the same issue but something tells me it is the OPO.
Update:
I just ran a quick test on my Nexus 7. It was able to stay "connected" for a straight 7 minutes. My OPO gave up after less than 1 minute (I have a script that runs every minute).
Update 2 (FINAL):
Welp, I seemed to have solved my own problem but I'll leave this here for anyone who is having the same problem.
I remembered that I did change one setting that was crucial to modify.
Yes, the dreaded Google Play Services wakelock issue... Went into Privacy Guard and re-enabled "Wake Up" for Google Play Services and what do you know, it fixed it.
Toggled it back off, and what do you know, it crapped out again.
So, it looks like Google Play Services is the culprit here. I guess the fix for now is to re-enable "wake up" while connected until the wakelock bug is fixed.
So, I occassion drive for DoorDash. When I do a system restore after factory reset the DoorDash app will mark me as paused. However, when I do a factory reset and just install a few apps the DoorDash app seems to work. It's seems like it tries to send me a delivery, but instead of it coming through it pauses me?
So I'm thinking there must be a conflicting app? What I'm wondering, is there a way for me to figure out what's causing the issue? I'll be able to watch the DD app, and know the exact time there's an issues if there are apps out there that could record internal issues or conflicts for me to analyze?
I know this isn't device specific, but this is my device. And I really could use help as DD support is beyond useless
hawki said:
So, I occassion drive for DoorDash. When I do a system restore after factory reset the DoorDash app will mark me as paused. However, when I do a factory reset and just install a few apps the DoorDash app seems to work. It's seems like it tries to send me a delivery, but instead of it coming through it pauses me?
So I'm thinking there must be a conflicting app? What I'm wondering, is there a way for me to figure out what's causing the issue? I'll be able to watch the DD app, and know the exact time there's an issues if there are apps out there that could record internal issues or conflicts for me to analyze?
I know this isn't device specific, but this is my device. And I really could use help as DD support is beyond useless
Click to expand...
Click to collapse
As long as it works via clean reset don't even bother trying to restore via any means if it is not necessary?
Just backup pics and data , and reinstall apps manually. There's a lot of reasons why conflict may arise - none of which is really within your means... If you're lucky MAYBE another app gets installed which causes conflicts such that uninstall would fix it but that's really far fetched...
To view logs you'd do something like adb shell logcat - start it on pc
Then make the app missbehave , and stop the logging on PC after ( With Ctrl+C )
Scroll through logs and see if there's any mention as to what's going on...
There's way more involved methods like injecting YAHFA into APK , then running your own logger for getting internal logsbof the app - If you can't even gather logs this is off the table lol
(You could attempt this via App Cloner tho , which is a paid app - like 2$ Select app, enable logs and rebuild app. I haven't tried the logging option so it might be 2$ spent on nothing if it does not work)
Either way - simplest option is factory reset then install everything manually if that causes no issues.
If you wanna backup / restore in future there's options to do it via adb , which might be more stable than system app
My oculus quest is having black screen issues. I did everything and nothing helped. Now I trying to set developer mode using mobile app to disable proximity sensor, but the app shows the error in the picture. it says "we are having problems try again". I tried a lot of things, I was able to set developer mode before factory reset. After that never worked again. My company account is verified. Now I'm trying to use logcat to debug oculus app to see if I can find something in logs, but I don't even know if it is possible. I saw I lot of messages but don't know the tag filter I should use. Any ideas?
i think you have to download the oculus SDK and activate it with it....
alexpfx said:
My oculus quest is having black screen issues. I did everything and nothing helped. Now I trying to set developer mode using mobile app to disable proximity sensor, but the app shows the error in the picture. it says "we are having problems try again". I tried a lot of things, I was able to set developer mode before factory reset. After that never worked again. My company account is verified. Now I'm trying to use logcat to debug oculus app to see if I can find something in logs, but I don't even know if it is possible. I saw I lot of messages but don't know the tag filter I should use. Any ideas?
Click to expand...
Click to collapse
Regarding setting developer mode and encountering an error in the mobile app, it's unfortunate that it's not cooperating(here). Since you've already tried several troubleshooting steps, it's worth reaching out to Oculus Support for specific guidance on resolving this issue with the app.
As for using logcat to debug the Oculus app, it's indeed a potential avenue for finding insights in the logs. When using logcat, you can filter messages by specifying a tag to narrow down the output. For debugging the Oculus app, you can try filtering by the tag "OVR" or "Oculus" to see if it provides any relevant information. Keep an eye out for error messages or anything that stands out as an issue related to the black screen problem you're facing.