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

Root [ROM][ALPHA][5.1.1] Dirty Unicorns 4/29/2015

modhatter6811 said:
He might not know how to get a log for that... @syrkles First things first, in development settings enable the built in terminal app if it isn't already, (you probably need a reboot after enabling it), then as soon as you get a random reboot, open terminal and type "su" enter, you'll get a root access prompt, allow it, then type the following into the terminal, "cat /proc/last_kmsg > /sdcard1/last_kmsg.txt" it should dump a text file of the reboot issue onto your sdcard. Grab that and get it to phenomx4. Remember to leave out the quotes when entering the commands. If you get an error trying to output the log, try sending out to sdcard0, which should be internal storage.
Click to expand...

I've never retrieved a logcat before. I don't have any particular need to at the moment either but I was hoping to just learn to do it. Thru Terminal, I tried entering the above with no success. I tried several other variations with no success but I couldn't simply copy and paste either.

Cat/process/last_kmsg > /sdcard1/last_kmsg.txt

Does that look right? I'm also using kk if that matters.
 
Briankd said:
Cat/process/last_kmsg > /sdcard1/last_kmsg.txt

Does that look right? I'm also using kk if that matters.
Click to expand...

The first term is the cat command - it has to be lowercase, cat, not Cat, and it needs a space after it.

Don't let autocorrect get you - it's proc, not process.

su
(wait for prompt to change to # sign)

cat /proc/last_kmsg > /sdcard1/last_kmsg.txt
 
"Briankd, post: 6966514, member: 1739922"]I've never retrieved a logcat before. I don't have any particular need to at the moment either but I was hoping to just learn to do it. Thru Terminal, I tried entering the above with no success. I tried several other variations with no success but I couldn't simply copy and paste either.

Cat/process/last_kmsg > /sdcard1/last_kmsg.txt

Does that look right? I'm also using kk if that matters.
Click to expand...

I'm going to assume auto correct changed that to "process" when you were typing.

Some tips here, use lower case, and be mindful of spaces, I'll use * to show you where the spaces are.
cat*/proc/last_kmsg*>*/sdcard1/last_kmsg.txt

And yes some times the ROM does matter, for instance my wife's phone runs ICS so last_kmsg does not work, in her case its simply called kmsg.

Edit; As EarlyMon stated, you must enter su first, without root access the file cannot be read.
 
Last edited:
I know how to get logs Dont have the time to get one need a functional phone at all times seems like only ROM that doesn't randomly reboot is aicp
 
syrkles said:
I know how to get logs Dont have the time to get one need a functional phone at all times seems like only ROM that doesn't randomly reboot is aicp
Click to expand...

You don't have 2 min to grab and post a log, yet you have time to get on the android forums and complain about an issue? If you aren't willing to grab a log when things like this happen, then why bother posting about it? If no one knows what error caused it, then no one can fix it. These ROMs we have are gifts, and they also have things like Alpha, and Beta in the names, implying that bugs should be expected. So, in other words, don't look a gift horse in the mouth. These are threads for development mind you, so if you truly need a functional phone, you're always welcome to go back to running stock.
 
Wow u people r funny i wasn't complaining just posting an issue I had. I'm not telling anyone to do anything about it just letting the dev know. Even the dev has posted before that he had the same issue so I didn't feel I was complaining. I appreciate all the work the devs here and everywhere do. Just posting about an issue sorry of anyone took it as complaining
 
syrkles said:
Wow u people r funny i wasn't complaining just posting an issue I had. I'm not telling anyone to do anything about it just letting the dev know. Even the dev has posted before that he had the same issue so I didn't feel I was complaining. I appreciate all the work the devs here and everywhere do. Just posting about an issue sorry of anyone took it as complaining
Click to expand...

Again I will reiterate by quoting myself, "If no one knows what error caused it, then no one can fix it." Many things can cause reboots. They usually occur when the kernel tries to do something it can't. There are potentially hundreds, if not thousands of errors that could cause a reboot. Without a log, simply stating that you have an issue, does nothing to help. Here's a hypothetical scenario to help illustrate that: I could be trying to use sms and get a reboot, and you may have simply tried using the camera and got a reboot. They would most likely not have been caused by the same issue, even though we both got the same end result. We need to know why it happened, hence the importance of having a log.
 
Here's a start. Looks like a good one
https://play.google.com/store/apps/details?id=com.tortel.syslog&hl=en

Seems fairly straightforward, it saves the logs to your SD card after you click "get logs". Then you can either send a compressed package of all of the different logs or select one in particular from the syslog folder.
I would imagine you could just use a simple file host to share it with the Devs.
 
Last edited:
What log do we generally need to grab for app force closes? I got that last_kmsg is for random reboots, but I figured I'd try to grab one that shows what's happening with the play store force closing.

.... I've got
*dmesg.log
*event.log
*last_kmsg.log
*logcat.log
*modem.log

... I'm guessing it's probably in the event log or logcat log, but I don't know what I'm looking for.
 
DsyMnapTic said:
Here's a last kernel message from a random reboot.
Click to expand...

DsyMnapTic said:
Happened again....

Including the logcat file too this time.
Click to expand...


I'm thinking these may have had something to do with screen off charging, as I don't think it rebooted again after removing my phone from charger. I went to sleep, so I don't know for sure, but looking back at my phone idle battery info, it's been idle since I unplugged it and went to sleep.
 
DsyMnapTic said:
I'm thinking these may have had something to do with screen off charging, as I don't think it rebooted again after removing my phone from charger. I went to sleep, so I don't know for sure, but looking back at my phone idle battery info, it's been idle since I unplugged it and went to sleep.
Click to expand...

I think thats some good insight, I haven't looked at the kmsg yet, but from the look of the logcat, the last thing your phone sent to the kernel, was a request to add a window twice. I have a good feeling it caused an issue with surfaceflinger. I'll take a look at kmsg soon, wanna move it to my pc, these phones don't like 1mb text files very much. This is fun!
 
modhatter6811 said:
I think thats some good insight, I haven't looked at the kmsg yet, but from the look of the logcat, the last thing your phone sent to the kernel, was a request to add a window twice. I have a good feeling it caused an issue with surfaceflinger. I'll take a look at kmsg soon, wanna move it to my pc, these phones don't like 1mb text files very much. This is fun!
Click to expand...

Lol, sorry dude....I noticed it was super lengthy when I tried looking through it to see if I noticed anything, but it's all foreign to me for now. Is it common that the file is that large?
 
starkraving said:
Looks like there's a lot of permission conflicts...did you restore app data from TiB, nandroid or have a dirty flash?
Click to expand...

My money says dirty flash, we did have that update to the ROM... or he might have forgot to wipe internal storage, I forgot to once flashing CM12, I had a lot of problems from that and force closes. I'm so happy you're still hanging around and helping us out, cause my knowledge really pales in comparison, and its always better to have more sets of eyes checking things out.
 
modhatter6811 said:
My money says dirty flash, we did have that update to the ROM... or he might have forgot to wipe internal storage, I forgot to once flashing CM12, I had a lot of problems from that and force closes. I'm so happy you're still hanging around and helping us out, cause my knowledge really pales in comparison, and its always better to have more sets of eyes checking things out.
Click to expand...
I know that CM has posted that to update there's no need to wipe data...that may hold true for official builds as they refer to dirty flashing as "updating normally"...but unofficial builds with builder mods and so forth...I'd always do a clean install. Just to give you a more accurate idea what's going on.
 
starkraving said:
Looks like there's a lot of permission conflicts...did you restore app data from TiB, nandroid or have a dirty flash?
Click to expand...

modhatter6811 said:
My money says dirty flash, we did have that update to the ROM... or he might have forgot to wipe internal storage, I forgot to once flashing CM12, I had a lot of problems from that and force closes. I'm so happy you're still hanging around and helping us out, cause my knowledge really pales in comparison, and its always better to have more sets of eyes checking things out.
Click to expand...

Nope, I clean flash everything every time I flash a ROM, even if it's an update. I actually do it twice to make sure. Also I didn't restore any app data in titanium....
Oh, do I have to wipe internal storage too? Just figured it's just like the SD card.
 
DsyMnapTic said:
Nope, I clean flash everything every time I flash a ROM, even if it's an update. I actually do it twice to make sure. Also I didn't restore any app data in titanium....
Oh, do I have to wipe internal storage too? Just figured it's just like the SD card.
Click to expand...
Strange...log reads like symlink/permission hiccups. Maybe try a full clean reflash. Try wiping the internal storage as recommended.
 
starkraving said:
Strange...log reads like symlink/permission hiccups. Maybe try a full clean reflash. Try wiping the internal storage as recommended.
Click to expand...

Maybe that's not what's causing reboots, I've only noticed random reboots with screen off and charger connected. What log do I need to grab for play store force closes?

I updated to B07 via Spock's fully stock ROM if that could possibly cause conflicts.
 
Last edited:
Ummm I cleaned things with SD maid and used a fix permissions app (that only fixed permissions of user apps) and I don't see any more unknown permission strings, or whatever you guys call them.
 

Attachments

Sorry for the ridiculousness, just trying to help. Here's the
*Kernel log
*Event log
*Last kernel log
*and the main log

This is after my last random reboot that occurred during screen off while connected to charger.
 

Attachments

You must log in or register to reply here.
Back
Top Bottom