• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root App to Keep Track of Reboots/Restarts??

scudder

scudder

Android Expert
Hey...

Was wondering if there is an app or widget that I can use to keep track of these "hot reboots" I'm having with the MikG ROM?? I mean, there is probably not an app specifically for that but was thinking some sort of battery monitoring app that I could look at...but was also wondering what I would be looking for in the stats, how I would read the data to see if/when I have reboots when I'm obviously not staring directly at my phone and notice them??

THANKS!!
 
Well I know when I restart the phone or gash another Tom there's usually a small glitch noticible in the battery times. I'm not sure if these hot reboots use enough battery while the phones starting to notice one tthough
 
argedion said:
I would try a logger program. Maybe that can give you some insight into the problem.
Click to expand...

You have one in particular you would suggest?? And how would I read/what would I look for...any idea??

I know when my reboots happen (in the house at least with wifi on) the following things happen: boots back up, wifi is lost, connects back up to 3G, then sync happens, then wifi reconnects. Perhaps look for that order or processes coming back in a row in a log...just wondering what program to use and what I would be reading??

THANKS!
 
Now that arg got me thinking about it, I would get logcat running on your device and then try to get it to hot reboot so someone can figure out what is causing it.

Logcat records each process that is happening on your phone... could be a huge clue to whats causing it.


I just realized how atrocious my first post was....damn it tapatalk ;)
 
Well, I just posted some NEW information that I think I figured out with regard to my ability to REPLICATE MY HOT REBOOTS!!! I posted here:

http://androidforums.com/evo-4g-all...lem-findings-your-thoughts-2.html#post4086451

PROBLEM is that (if you read) the app I was using "System Tuner" to view the logs is not saving the logs automatically. I have to click "save" and CANNOT do so in the seconds before the reboot.

I saw that you guys suggested "logcat" above...I found "aLogCat" and that app has the ability to periodically save the log files however there are a couple problems:

(1) I don't see a timestamp on the scrolling log files. System Tuner has time stamps in MILLISECONDS if needed.
(2) The interval for periodic automatic saving is only as short as 15 minutes.

Is there any other app or technique that will log EVERY log message?? I need it to run for about 30 seconds to 2 minutes...and up until THE MOMENT that the reboot is triggered and about to occur.

THANKS!!
 
scudder said:
Well, I just posted some NEW information that I think I figured out with regard to my ability to REPLICATE MY HOT REBOOTS!!! I posted here:

http://androidforums.com/evo-4g-all...lem-findings-your-thoughts-2.html#post4086451

PROBLEM is that (if you read) the app I was using "System Tuner" to view the logs is not saving the logs automatically. I have to click "save" and CANNOT do so in the seconds before the reboot.

I saw that you guys suggested "logcat" above...I found "aLogCat" and that app has the ability to periodically save the log files however there are a couple problems:

(1) I don't see a timestamp on the scrolling log files. System Tuner has time stamps in MILLISECONDS if needed.
(2) The interval for periodic automatic saving is only as short as 15 minutes.

Is there any other app or technique that will log EVERY log message?? I need it to run for about 30 seconds to 2 minutes...and up until THE MOMENT that the reboot is triggered and about to occur.

THANKS!!
Click to expand...

It was suggested to me to use the app "catlog" to save the log information. I downloaded catlog and set the app to "record" the scrolling log file. The PROBLEM is that as the phone approaches the reboot and, in fact, reboots, the log file is NOT SAVED. I come back and relaunch the app and there is NO FILE saved. Although I can start to "record" it appears that I have to "end" the recording session to save the file. It is NOT saved on the fly as it happens...

Hope you understand the problem...anybody have workaround??

THANKS!
 
Logcat runs from your computer using the android sdk and it will save a log file of everything that goes on untill you kill the process. So you start it up and do whatever you need to do to create a hot reboot and then stop the logcat and review it/send it to the devs
 
Rxpert83 said:
Logcat runs from your computer using the android sdk and it will save a log file of everything that goes on untill you kill the process. So you start it up and do whatever you need to do to create a hot reboot and then stop the logcat and review it/send it to the devs
Click to expand...

Uh oh...that's a problem. If I have to hook up to computer, my data/charge port is d-e-d, dead!
 
Rxpert83 said:
Logcat runs from your computer using the android sdk and it will save a log file of everything that goes on untill you kill the process. So you start it up and do whatever you need to do to create a hot reboot and then stop the logcat and review it/send it to the devs
Click to expand...

ASSuming that I can plug my phone into the computer :eek::eek::D is there an EASY way one goes about setting up android sdk and what aamikam at theMikMik forum has asked me to do with using "adb logcat"??

FORGIVE ME but I checked the following page and I am NOT familiar with sdk or adb:

logcat | Android Developers

I'm more at the moment like wtf lol when I look at the stuff :D:D

Help...:confused::confused:

THANKS!!
 
scudder said:
ASSuming that I can plug my phone into the computer :eek::eek::D is there an EASY way one goes about setting up android sdk and what aamikam at theMikMik forum has asked me to do with using "adb logcat"??

FORGIVE ME but I checked the following page and I am NOT familiar with sdk or adb:

logcat | Android Developers

I'm more at the moment like wtf lol when I look at the stuff :D:D

Help...:confused::confused:

THANKS!!
Click to expand...

yes seems to be getting overly complicated just to get a log file to tell you whats going on. Like you I'm not familiar with sdk or adb I was really hoping a simple log program could help here.
 
argedion said:
yes seems to be getting overly complicated just to get a log file to tell you whats going on. Like you I'm not familiar with sdk or adb I was really hoping a simple log program could help here.
Click to expand...

It appears that the log programs that don't run info to the computer will give log information basically UP UNTIL THE PROCESS causing the problem IF at all. The two apps I tried don't even save ANY log file that was set to be saved even if the "recording" of the log file starts minutes before the reboot. Once the reboot happens, the log file that was slated to be saved it gone.

I guess if the log file is dumped to the computer the computer is capable of saving it up until the precise moment of the reboot...and that is what is needed.

I haven't tried to dump the file from my computer yet...FIRST have to see if I can get the connection going with my bad port, then have to find someone to walk me through the sdk adb idk wtf lol!!??:eek::eek:
 
Well if that don't work I hear smith and wesson has a permanant solution :D:D:D

Is Mik the only rom that does it or are others doing it as well? I think you said they were but don't remember and to tired to scroll back and glance at all the other threads :p
 
argedion said:
Well if that don't work I hear smith and wesson has a permanant solution :D:D:D

Is Mik the only rom that does it or are others doing it as well? I think you said they were but don't remember and to tired to scroll back and glance at all the other threads :p
Click to expand...

Rxpert83 said:
If I remember other ROMS are having the issue as well but Tommy's Classic is stable for him
Click to expand...

And if I remember...I'm having trouble doing that myself lately!! :eek::eek:...I had problems with NoLimit06, was fine with Tommy Tomatoe and hot reboots with MikG

And argedion how DARE you suggest a gun...I would NEVER hurt my EVO!! :mad:
 
argedion said:
hmmm that is interesting is it all other ROM's or only Sense ROMs? If Tommy's is working good for him then he should just ditch the MikG and stick with tommy.
Click to expand...

I have not tried any AOSP ROMs. And it is NOT all Sense ROMs. Tommy did work but, I'll tell ya, too, too stripped down for me with that Sense 1.0 feel :(

So, not only am I spoiled but I'm on a bit of a quest (crusade perhaps??:eek:) to try and get this fixed!! :D I have been in contact with the dev aamikam at theMikMik forums gave him a bunch of information (what I've posted here and at http://androidforums.com/evo-4g-all...lem-findings-your-thoughts-2.html#post4086451 trying to get a log file to him.

I also kinda sorta have a few work-arounds. One is to put the screen timeout to 10 minutes and MAKE SURE that I shut the screen off manually. That why I avoid whateverthehellhappens right before the screen timeout kicks in triggering the reboot. Secondly, it appears that a periodic "full/normal reboot"...shut down, and restart...flushes/kills whatever becomes active in the background that contributes to the hot reboot. I am NOT SURE how long the normal/full reboot stops the hot reboot though.
 
argedion said:
hmmm that is interesting is it all other ROM's or only Sense ROMs? If Tommy's is working good for him then he should just ditch the MikG and stick with tommy.
Click to expand...

There is a ROM that looks promising that was suggested by ocnbrze in my over in my MikG 3.1 Hot Reboots thread that is MikG 3.1 based with Sense 2.1+ and can be found here:

[ROM][evo4gnoob] HayzdaROM RC1 - Why do roms have mottos..? [Sense2.1-3.0] - xda-developers

Looks very interesting!!...but if "MikG 3.1-based like it says" it might have the hot reboot problem that I'm suffering from baked in. Need to try though...
 
Hey scudder, I was just thinking, you said it happens when you're on wifi....

Well, could your wireless router may be able to help you time it? I know some keep track of DHCP addresses given out, well, maybe you could see if there are any records of when DHCP addresses are leased and when devices are associated with the AP....

Maybe? It's obviously not as good of a solution as something the monitors the logs but...

Also, based on the fact that the logcat files are deleted upon reboot, I'm guessing they are saved to /tmp? If so, is there an option to save them somewhere else, like maybe /sdcard/log
???

:) best of luck!
 
9to5cynic said:
Hey scudder, I was just thinking, you said it happens when you're on wifi....

Well, could your wireless router may be able to help you time it? I know some keep track of DHCP addresses given out, well, maybe you could see if there are any records of when DHCP addresses are leased and when devices are associated with the AP....

Maybe? It's obviously not as good of a solution as something the monitors the logs but...

Also, based on the fact that the logcat files are deleted upon reboot, I'm guessing they are saved to /tmp? If so, is there an option to save them somewhere else, like maybe /sdcard/log
???

:) best of luck!
Click to expand...

Ummm...wasn't really having a issue associated with my wifi, just with trying to get the log information I need AND saving the log file.

Apparently what I need to do is wirelessly or though hooking the phone to the computer with Android sdk and an adb command, have the log file LIVE ON THE FLY transferred to the computer so that up until the very moment the reboot happens, the log file will be saved on a device separate from the phone.

I will look into the /tmp thought...thanks!
 
scudder said:
And if I remember...I'm having trouble doing that myself lately!! :eek::eek:...I had problems with NoLimit06, was fine with Tommy Tomatoe and hot reboots with MikG

And argedion how DARE you suggest a gun...I would NEVER hurt my EVO!! :mad:
Click to expand...

I WOULD NEVER SUGGEST SHOOTING YOUR EVO :D:D:D:D:D

That would be just MADNESS I SAY:p
 
Just letting whoever is interested or following this hot reboot issue that a buddy Gamblor01 over at theMikMik forum was able to replicate what I found with my hot reboot issue where it was happening juuuust before the screen would timeout according to the Display settings.

My buddy thinks that he got a log file capture during a hot reboot!! Keeps ME from having to save a log with my port issue :D SOOOOO, he's gonna send over to the dev, aamikam, and we'll see what happens.

I'll keep you all posted...
 
scudder said:
Ummm...wasn't really having a issue associated with my wifi, just with trying to get the log information I need AND saving the log file.

Apparently what I need to do is wirelessly or though hooking the phone to the computer with Android sdk and an adb command, have the log file LIVE ON THE FLY transferred to the computer so that up until the very moment the reboot happens, the log file will be saved on a device separate from the phone.

I will look into the /tmp thought...thanks!
Click to expand...
Okay, yeah, I was just thinking if your wireless kept track of association times, then you'd know when it was rebooting, which I thought I read somewhere, but I could have just thought I read it, it was a long day yesterday ;)


Hope it all works out, and I'll be keeping track of this thread. ;):D
 
You must log in or register to reply here.
Back
Top Bottom