[Motorola Droid RAZR] Ohmster:
Oh my, I am really sorry to hear this, [MENTION=3668995]Meneldur[/MENTION]. I for sure do not want you to recreate problems if you do not have to. I would much prefer you to get a good running system and be happy with it. :)

Look, I went through this situation for almost 10 months. There were always a certain "few" Senior Members who "Never had a problem with their phone and it always ran slick, fast, and smooth as butta". And they proved it with screenshots, benchmarks, and their word on performance reports. These few members would not lie, they do not have that sort of character profile to be liars. They are honest, very likeable, friendly, but are "keep to themselves pretty much sort of people". They do not "brag" about their phones, they do not have issues that require them to ask for help, they do not feel anyone would be interested in their own personal phone and it's configs, so, you hardly see them here very often. They occasionally show up to answer a question or two, and did respond to my plea for help. I had to interview most of them with very specific questions to slowly get out of them the secrets of their success. And I got a LOT of very good answers and saved them as text reference files. [MENTION=3322848]JakeDHS07[/MENTION] was one very skilled individual who could help a lot, but he tore his own phone down and started from scratch almost every other day, doing build reports, new kernel tests like JBX, and helping others so much that he never really had much "uptime" on his phone. I could not ask Jake/Shaun. And I kept getting "Go clean, go clean" answers from so many members trying to be helpful but within a week, my phone would be the same after I restored all my "junk". I was missing something important. :confused:

I combined things from so many experienced members in a setup that would work for me and started over, from scratch to get this done. I actually "Formatted" my internal sdcard in Safe Strap while mounted in Windows because I wanted to be absolutely clean. Bad idea, I lost my /pds folder by doing this because I did not know to back it up. And afterwards, my LTE chip no longer worked so I had to get a refurbished phone from insurance. But, I started fresh with this phone anyway. And I got it right! I did make a lot of backups along the way especially of the new install, right after finishing the setup wizard and shutting off play store updates and labeled this backup "base" with build and install date. I could restore this anytime and try again. I probably made 4 backups in the time it took to start fresh and get the system the way I wanted it. And I had to restore some of them because I did not always get it right.

Oh my, I am taking way too long with this. Sorry, will try to speed it up a notch. I wrote a Guide for you and have since updated it several times. I am not "the best" member to write this guide, but I am the only member writing this guide so it is all we have. I do not know for sure if you did follow that guide, step by step, to rebuild your phone. Or what steps you skipped. I probably would skip several of the 18 steps thinking I know better and might grudgingly have to do it all over again and this time, really do everything. And learn along the way what to avoid.

So what happened truthfully? Did you redo your phone as per the guide? Did you skip anything? It is your phone, I will not be upset, only you can decide what is right for you. Is your phone better now than before I answered your help request and if so, why, what did you do? Just trying to help not only you, but to fine tune the guide to help everyone because no other guide exists, AFAIK.

What is Instagram? Can you give me a URL to whatever it is please? This is what you believe triggered this slowdown on the phone? My phone really does work as slick as snot or realistically, as fast as you can expect a Razr phone can go. You took out all the tools so I believe you did make some effort to redo your phone. I asked you to not reinstall them because you were "fine tuning" an obviously broken system and these kind of tools are not for the average user. They do not yield large performance gains, only slight ones for very well running systems. I do not use them because I do not need them, or the hassle of dealing with them. I did reinstall Trickster only to reset my min/max CPU frequencies. For some reason, my phone would now idle at 600 instead of 300MHz. I ONLY turned on the frequency set portion of Trickster and set it to restore on boot. My phone again spends most of it's time, idling at 300MHz per Wakelock Detector.

Thank you for writing back, I really was wondering how you made out and want to know if you are now okay. And to know what, if anything, needs to be done to update the guide and I have since updated quite a few things on that list and numbered them so people can ask about #2. #7, #12, or whatever they want. Work with me [MENTION=3668995]Meneldur[/MENTION] and let's fix your phone, bro! Not so much for me but so you can be happy with your phone and to prove to others in the same boat, "It can be done." :D

This is The Updated Guide.

How to install and maintain CM11 for a good running phone

---------- Post added at 11:35 PM ---------- Previous post was at 11:24 PM ----------

Hello Daniel.

I'm done with bills, dinner, and can take the time to give you a good reply now. Shower can wait. ;)

Let's do the easy stuff first. Finding your car when you park it and leave. On my stock Verizon JB rom, it came with a really neat app called "Car Compass" and that very same, very good app is available free at the play store, Car Compass with a 4.0 rating. Check the link, the app is pretty impressive and does not load your system down because it does nothing until you use it. Then it acts like Maps to mark your GPS location on a map when you exit the car. Exit the app and go about your business. When you want to find the car, open the app, see your car on the map, and go right to it. Works great unless you are in an underground parking garage with no GPS signal available. In that case, peg the location when you exit the garage. You also get terrain view besides just a map to find your car in a vast parking lot. Pretty neat and I do use this app. :good:

Finished with Build Report 11/03, rom is very, very good. CPU frequency is due to something else, fixed it with Trickster for now. I got my 300MHz idle back and have decided to use the INTERAVTIVE CPU governor instead of ONDEMAND. The Guide I published has been constantly updated to reflect the changes. So if you want to get a newer, for sure confirmed good rom, 11/03 I can swear by, updating to 11/06 now and will report. But hang on a minute before you just "update".

I see that you are not happy with the performance of your Razr on cm11, or perhaps, at all and have had this issue for quite some time, yes? I see this complaint all the time and I was one of the loudest complainers in the thread, "CM11 is just not a good rom anymore". :(

NOTE: I am going to refer you to the [MENTION=3668995]Meneldur[/MENTION] post later down in this message. You do not have far to go, it is the very same post you are reading, just above yours. ;)

My cm11 started out great, was amazingly fast, then just deteriorated over time to a poky, slow, problem laden phone so bad I could not really rely on it anymore. E.g.: I have to get to a doctor appointment in 20 minutes and need GPS to get me there. Trying to get Maps and Navigation open, running, and ready to go took so long that I would miss the appointment! I miss calls because I cannot get the screen to light fast enough. I cannot hang up because the screen goes dark and will not light up fast enough to end the call. And the overall performance is just plain ....SLOW. Bad news.

And I was not the only one. There were several members echoing my complaint. AT that time, we have and had several Senior, very experienced members, who would report that their phones were running fast, no issues at all, and were smooth as "butta"! ...huh? Butter? You mean more like ice cold asphalt tar, don't you? :p

...uh, [MENTION=3668995]Meneldur[/MENTION] is having a similar issue as well as [MENTION=5362796]Dwillian[/MENTION] and some other members. The only difference is in severity of the situation. I created a guide for this and just went over it again with Meneldur. Please jump down to Post #6568 to pickup on the story and the instructions. Your Razr should work like mine does now. Fast, responsive, always ready, no issues, and is as fast as a Razr phone on Kit Kat can be. I have no urgency to update because this really is, a terrific, albeit somewhat dated, $600 smartphone.

Go down to the Meneldur followup and then see if you are willing to redo your phone per the Guide to finally clean it out and make it right. I am not an expert at this, but I did get it right enough to be satisfied and am constantly updating this Guide. You are a really laid back kind of guy, Daniel. So "all this work" I am sure you are not happy about and may simply just "put off" for a long time or forever. But you cannot blame the cm11 rom until you give it due diligence, clean up the phone and do proper maintenance on it, and get it right. It amounts to shutting off just about everything you do not use or need, keeping it minimal but install the things you want, getting it right and keeping it that way. AND, you will have to make a LOT of Safe Strap backups along the way. LOL! :laugh:

What do you think, are you going to "let it ride, Casper style", or get off yer butt and "Git 'er done", Larry the Cable Guy style"? Just kidding, only using his phrase, not his lazy ass style, bra! ;)

How to install and maintain CM11 for a good running phone

OFF TOPIC: Just updated OTA from 11/03 to 11/06. Looks good but too early to give a build report on it. I can swear by Nightly build 11/03 right now though.

---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------

Yeah, could not agree more. But Chainfire needs a new, Lollipop device to own for him to bother with it. LOTS of members in here took the Turbo deal and now hang up their root hats, terrible shame. But the Turbo has yet to release the promised Android L OTA update yet and I bet that won't be at the top of their to do list. But it should be.

You know, Brian, that I really thought that "Chainfire" was a corporate name instead that of a single developer like Hashcode. Chainfire, Hashcode, Matt Grolf, Dan Rosenberg, and yes, stargo in my book are the heros of our generation and we should all be familiar with these names. True, Michael Gernoth, stargo, has not built Safe Strap, SuperSU, or even created a nice rooting script, but he has helped everyone in this group many, many times. Some of us, personally all while developing cm11 for OMAP4 devices. If he pulls off his latest ambition to make Lollipop work on Droid Razrs work and successfully get them into the CyanogenMod CM12 Build Tree, when they clearly do not meet the specifications required for it, I will be Amazed and stargo will really rise to the Godlike status of the other guys like Chainfire. :D

When I lost my phone's 4G and heard that the phone itself is toast and there is no way to fix it, I wrote to Matt Grolf to ask him if were really true and if there is anything at all I could to do restore it via system. He actually personally wrote back and confirmed the worst. He said it was rare but he has seen it and it is a done deal. Once the LTE chip burns out, there is no way to fix it (Aside from chancing to by a broken screen XT912 from eBay and swapping out the mother boards.) and I had better look for a new phone. I never thought he would answer someone like me. :o

So who is going to be a "nice guy" and buy a non-developer edition $700 Turbo phone when it gets the Lollipop update and give it to Chainfire? :p

EDIT:

Some very interesting stuff for total Geeks by CyanogenMod. Never saw this page before. Can even build your own CM11or kernel!

Information: Motorola Droid RAZR/RAZR MAXX (CDMA) ("spyder")