[Motorola Droid RAZR] Ohmster:
I just reported that I restored my 11/28 backup and my MIN and PRL settings are populated, FYI. But my orange bars are back with a vengeance. We have already heard from our Turbo user brethren that the orange bars are not a CM rom issue, but do happen frequently with stock Verizon roms. I will update when something else comes along that looks promising or might even drop back down to 11/07 by using the Dwillian Dump so I can save my current apps, settings, and install an updated pa-gapps package. I think that is my best option for now my friend. You are not alone on the 11/07 build. I will tell you if my PRL or MIN is not populated. Yeah, I am going to downgrade to 11/07. I really think that the 11/07 rom has the "Blueprint Polish" that I am describing below. It is not like I am missing out on any features with this slightly older rom or anything. The phone really works perfect on that rom, so why not just use it until something really well build comes along?

That sounds like a good plan, [MENTION=5362796]Dwillian[/MENTION]. I am sure you do not need instructions, Dwillian, but I will give them for the benefit of anyone wanting to try this. Save your so far good running build of CM11 11/07 and wipe the slot, recreate with your preferred partition sizes, and install NIGHTLY Build 11/07 with an up to date set of pa-gapps and see if this changes when you boot to system. Since a new rom takes a few minutes and maybe a couple of reboots to "settle in" (Rebuild the Dalvik Cache, System Cache, sync with servers, and update phone, system, and App settings.), allow several minutes of run time and reboot again, allowing a few minutes to see if this changes anything. If not, well, you have your answer. Let us know, okay? :good:

I notice that the past set of roms are not as "nice" as the previous set. I bet these later release roms would run really well on a modern smartphone like a Samsung Galaxy Note 4 or something else new and powerful. Our phones are over 2 years old. Moore's Law states that every 2 years, computing power would double and that has been pretty much true for the past few decades. For a rom to work really good for us, I think it would have to be extremely well "Polished", like precision parts machined to make a race car engine. To "Blueprint" an engine, they tear down a brand new engine, machine each part to be within 1/1,000th of an inch in tolerance, and the engine now runs so well and smooth, that there is a significant gain in speed and performance. For these new CM roms to work well for us, they would have to be near "Blueprint Perfect", IMHO. That is my definition of a good CM rom for OMAP4 devices, "Blueprint Polished". :D

That explains to me why these roms are such a crapshot. On my Samsung Galaxy Tab 2, 10.1, I almost

never

have a rom related issue. CM11 always performs well and beats the pants off my Droid Razr Max every time, even though the Dual Core Processor is 1GHz and the phones have a Dual Core 1.2GHz Processor. So, expecting every rom to work well is maybe a stretch for us. Besides outdated technology, we also have the proprietary "Motorola Blob" issue where the source code for the inner workings of the Motorola device are not made public and are not available to the rom developers. Then Stargo has to "workaround" this issue with a "binary blob" in the code. Very inefficient to say the least, if not impossible to do.

This is all my opinion and in no way is proven factual. Believe what you will. Thanks you all for listening and for submitting your own reports! :good: :D

Members, we all need and want good build reports so we know what roms are good and which to avoid.

Please be kind and Tap The Official Thanks Button for contributing Build Reporting Members.

These are very helpful posts and we want to encourage More, Quality Build Reports in this thread. The Thanks Button is there for just that very reason. Thank you! ;) :good: