[Motorola Droid RAZR] Ohmster:
Dwillian is giving you good advice. If he does not mind, I will add my own experience to his to help you with your question.

I use slot 1 for any CM rom. Since space is always at a premium and I have a great rooted blur Verizon rom on stock, I think I used the infamous Matt's Utility to get this and it is perfect, I put CM 10.1 on slot 1, then updated it to 10.2 when that update became available, and now CM11, I do not have card space for another rom, although I might be mistaken, the slot may be able to hold another rom, but I would have NO card space for anything at all for another rom. So, I first backed up my CM10.2 because I had it perfect, then replaced it with CM11. Always slot one. I have heard few others have put CM11 on stock slot, very few reported it works great, no problems at all, others say it won't work or was a disaster. To me, it makes no sense to put CM11 on stock slot, stock is your main, reliable, always works stock slot. I always keep a very good, working, blur (Verizon Original w/out all Verizon bloarware) stock rom on stock slot.

This works good, both of my roms are now working great. For the times when CM11 was too unstable and would fail during the day when I need a solid phone, I would revert to stock because it always works. Now that I have a totally clean install of cm11 1/30/2014 and gapps only (I started with 1/27/2014 and updated through system OTA to 1/20/2014) on slot 1, so far, so good. Only once did I have to wipe dalvik, but that was it. Release 1/30/2014 release notes said this release addressed issues of a dalvik leak. Since my issues were always caused by a slowly corrupting dalvik, I took that update right away. So far, so good. No need to reboot or wipe anything, nothing is broken.

When you get a good cm11 system running, clean install, cm11 and gapps only, (You can add xposed framework apk and modules if you like, just don't go nuts with the modules right away.) until it runs a least a week solid. Then if it passes this test, you can add JBX kernel if you want it. I think it is very nice, and I love the trickster panel for it. But until I get a stable rom that can run an entire week w/out having to reboot or wipe anything, NO other changes! It is extremely important that you get a good, solid install of CM11 and prove it before adding kernels and other mods and backup that system if it passes the one week run test. You MUST make a one backup of a solid rom w/out complicating it beyond flashing cm11 and gapps. Nothing else! Then, if need be, you can always restore this backup if you later add a new kernel or flash other mods or changes. Good job Dwillian!

---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------

You can download CatLog - Logcat Reader from the play store. It works very well, filters for you, saves logs. There are many log readers on play store. You can also view, filter, and save syslogs from xposed module Android Tuner Free on page 4, System and Kernel Logs.

I do not know the details of what your friend wants you to log. Last time I needed Cat Log I used it to help a developer make my phone blocker work on my Droid X after Jellybean was flashed, it would no longer block anonymous or blocked caller ID calls. So, I ran Cat Log, block my caller ID by prefixing my home to cell call with *67. Then seeing the call was not blocked. Stopped Cat Log, and filtered for "call", thus getting rid of anything not pertaining to a phone call and the developer found out that Jellybean used a different word for blocked or no caller ID calls. I still have that email with zip attachment of the log to the developer in my mail! Yeah, we needed it because Jellybean did not call an anonymous call "anonymous" anymore so my fantastic call blocker gold stopped working. The developer did not have a phone like me so he asked me to save some logs. Run Cat Log, make a regular call, hang up, make a caller ID blocked call, hangup, and send the log. The line in the logs of interest was this one:

06-21 00:43:55.368 V/blacknWhite.CallBlocker.Gold(14167): Processing incoming number: ABSENT NUMBER

As it turns out, Jellybean on my Droid X now resulted in the call being "identified" as "ABSENT NUMBER", not what he programmed into call blocker from past releases.

You could use the call log history to add entries to be blocked, your contact list, or, Jaimie, (The Developer) only put a numeric pad for new blocked call entries. I could not input "ABSENT NUMBER" into a numeric key input pad. Either he had to make constant changes and test them with me (He did send several updated apk files for me to test.) or send me a special version with a full alphanumeric keyboard so I could enter anything I wanted as a blocking element. He sent me a special version like what I wanted. So I entered "ABSENT NUMBER" in the box of what to block, my phone would no longer ring on anonymous phone calls!

This is a real life example of what a log cat is and what it can be used for. In Linux, that file is called "messages", is very huge, and gets lines added to it for everything that happens. Great for hunting problems, but horribly large if you do not apply filters to trim it down for what you want to look for. Linux is open source and free, so Google used it to make Android, a special, very trimmed down version of Linux, with some special stuff necessary for phone use. (Apple computer uses Linux as it's OS but it has been specialized for commercial use and the license is not free. It is owned by Apple and they share it with NO ONE. That is why Apple hardly ever gets viruses. Linux is not "virus friendly" because hardly anything runs with administrator privileges, unlike Windows, where everyone is an Administrator, thus, anything that occurs on their login has full administrative privilege to install something like a virus.) Now you know, good luck. :good:

If you found this post helpful, please put a penny in my tip jar, the Thanks button! :laugh: