Is there a way to determine what specifically caused a reboot or maybe the state of the phone right before a reboot? I'd like to find out what exactly is causing my phone to randomly reboot. If I could pinpoint an app that is causing the problem... problem solved!
Does a "reboot analyzer" type app exist?
Yes. Try alogcat in the market. Logcat can run in the background so it will catch what's causing reboot. If you don't know how to read a logcat theres a logcat reader in the market or just post the text file and someone could read it for you. It doesn't kill battery faster than any other app or nothing like that so don't be worried, just let it run.
Its not just a reboot analyzer it will tell you everything thats going wrong with your device etc. You should take some time to learn how to read it. Pretty neat..
Edit: I had some force closes with alogcat so download catlog it works great!
Thanks for the alogcat recommendation. You're right, I definitely need help reading it. What is the best way to learn what the logcat means? Right now, it's completely greek to me and I actually have a programming background (vba, c++, fortran).
sjamie said:
Thanks for the alogcat recommendation. You're right, I definitely need help reading it. What is the best way to learn what the logcat means? Right now, it's completely greek to me and I actually have a programming background (vba, c++, fortran).
Click to expand...
Click to collapse
Use catlog it will help you read it. Try opening catlog then turning your phone in landscape to get a feel of how it works!
http://developer.android.com/guide/developing/tools/logcat.html
http://forum.samdroid.net/f38/tutorial-how-get-logcat-example-check-battery-drain-2543/
Try searching around or visiting the android homepage for devs. Lots you can learn there.
Related
Hi,
Is there any way to get a logcat report of the phone without using ADB?
I'm on my work machine at the moment and it's doesn't play well with ADB but I need to get the report so I can submit it with a bug report (in VR12, when using an app or in a menu, pressing the Back or Home keys crash Sense and it has to reload - no process managers being used though).
Thanks.
I was once told about an app on Market called something like log grabber, log catcher, log fetch or something along those lines. Have a look to see what you can find. Ill try to have a look later if i can for you. Let me know what you find.
Just had a quick go then, you can just type logcat into a terminal emulator. Not sure about outputting it though, you will have to see if anyone with more Linux experience than me knows.
Sent from my HTC Hero using XDA App
Thanks for that, I couldn't find any of those you mentioned but have found Log Collector and aLogcot so I'll give those a try now and see which one is best
alogcat works perfectly.
I've attached my log but will also post in the appropriate thread.
Thanks for the help folks
I'm gonna say it loudly. I did not make these apps., so don't tell me this a repeated thread. I'm putting it up for the noobies.
Now to begin. So, what is a verbose boot? Well, it tells you exactly what is going on when you boot up a Nook.
Let's start! Your gonna need two apps. They're called "root live dmesg boot" and "root live logcat boot"
They cost I think 3 smackers total.
Got those? OK, now open up settings. Find these to apps in applications and hit move to phone for both.
If there isn't that button and it says move to sd card, you are OK!
Now open up the dmesg one. Dish out a superuser access.
Hit install live dmesg. If it is grayed out, good.
Check hide copyright.
Unless your screen is 10 inches or bigger, DON'T be a double sizer.
Change starup mode to split.
Now, your wondering, Why did I download logcat?
Well, dmesg it the boot process and the logcat it the log. It shows both on boot up.
Fire up logcat. Same options.
But now hit reboot.
Wait, and do you see code?
Is it cool?
For some people this is old news, like pndo1.
Credits!
@pndo1 for telling me about live dmesg.
@Chainfire for the apps.
ive ran this app and it is pretty neat.
Sent from my NookColor using Tapatalk
Live Boot
@ikingblack
You don't need both of the apps, you only need one. You can pick either one, it really doesn't matter. Just pointing this out so people don't get confused.
You need both to display both at the same time in "split" mode ...
@Chainfire
Thanks for pointing that out. I had no idea it worked like that.
Okay so I'm trying to get an app to autorun whenever my phone boots. More specifically the app "Screen Filter".
So far I've found the app "autostart.apk" that claims it will autorun the file /data/opt/autostart.sh
Basically I'm asking how do I make this autostart.sh file and place it in that directory?
If it helps, here is the 'receiver' info about Screen Filter
- com.haxor.ScreenFilterWidget
--> android.appwidget.action.APPWIDGET_UPDATE
--> com.haxor.ScreenFilter.ACTION_FILTER_TOGGLED
- com.haxor.LocaleReceiver
--> com.twofortyfouram.locale.intent.action.FIRE_SETTING
Any help is appreciated! Thanks!
dew1989 said:
Okay so I'm trying to get an app to autorun whenever my phone boots.
Click to expand...
Click to collapse
I believe you would have to edit the AndroidManifest.xml for the app and use the BOOT_COMPLETED intent.
I'm not sure if there's an easier way to autorun apps after booting.
Are you able to guide me to the details on this? I understand what you're saying I just am clueless on how and what to do
I've never done it before. However, you might want to try this link as a guide:
http://stackoverflow.com/questions/1056570/how-to-autostart-an-android-application​
Wow that is thoroughly confusing. Where do I get these files that I need to edit? I am rooted by the way
dew1989 said:
Wow that is thoroughly confusing.
Click to expand...
Click to collapse
Oh wait. The example I linked to earlier is more development-level information. To use that with an existing application, you'd have to decompile, edit, and then rebuild, sign, blah, blah.... Sorry about that.
Not too sure on how to use 'Autostart (Root),' though. If I can figure it out later, I'll add to this thread.
Have you tried emailing the creator of 'Screen Filter' (https://profiles.google.com/bslatkin/about) to see if maybe he'd consider adding a launch-on-boot option to his app? It appears he works at Google, and the app is small, so he might be persuaded to do a quick update.
is there a log file i can look at to give me a clue of what is cause the reboots?
Anyone knows?
Could be anything. Try giving more information?
I am just inquiring, if there is a log file somewhere that i can see so that i can track which app was being launch or services so that i can see what or figure out what is causing the reboots.
supac said:
I am just inquiring, if there is a log file somewhere that i can see so that i can track which app was being launch or services so that i can see what or figure out what is causing the reboots.
Click to expand...
Click to collapse
look for logcat on the Market...it will do this for you...
i noticed mine rebooting too, i am on saurom and it only happens when i set my CPU to 1944000.... might want to check that
So I've had to use logcat extreme for a while since it's the only one that would work consistently. Now it's crashing and it appears Matlog is active again. I can't get a logcat to consistently display. Most of the time nothing shows. And well I'm not really sure how to debug without a logcat. Done all the typical steps of clean flashes and such.
I've always used Catlog, if I'm not using a toolkit app's bundled reader or the ADB console window.
Speaking of which, have you tried hooking up to your computer and pulling it via ADB?
Septfox said:
I've always used Catlog, if I'm not using a toolkit app's bundled reader or the ADB console window.
Speaking of which, have you tried hooking up to your computer and pulling it via ADB?
Click to expand...
Click to collapse
I just don't always have my laptop on me. That's all. I've figured some stuff to make the logcat show but it's just annoying.
TotallyAnxious said:
I just don't always have my laptop on me. That's all. I've figured some stuff to make the logcat show but it's just annoying.
Click to expand...
Click to collapse
Oh, I know. It's definitely not an ideal solution.
But using the ADB console to run logging (better yet, have it stream to a text file so you can search by the package name after launching the offending apps a few times), you can open up your apps and see what error(s) they're throwing. Use logcat to debug logcat, like.
https://play.google.com/store/apps/details?id=com.sungroup.logcat
This works for some reason. It's clearly a fork/clone of MatLog but it works everytime.