[Motorola Droid RAZR] Ohmster:
Michael,

I have nothing but good news on my end to give you. Currently running CM11 02/08 and have not had signal problems but from maybe almost 2 weeks ago, prior version. My bars dropped to like 2, then 1. I made a test call. Within 10-15 minutes, I had No Signal. I rebooted and at that time, always wiped dalvik. It fixed me right up. At that time, you were saying a vanilla reboot was all that was required as you built a modem reset script into the current releases. Not since have I lost service again. My bars do dip and clip, but nothing serious. My signal now is -80 DBm and that is good for me.

Not sure by what you mean by "you do not have a spyder to test on". What is technically "spyder"? A Motorola Droid Razr phone? Be it a Razr, Razr Maxx or Razr HD?

My phone is a Motorola Droid Razr Maxx, Verizon US XT912 and for several releases, it has all been good. No jbx kernels, I have a few xposed modules but use them mainly for nice icons and to keep screen on for certain apps like maps, does not make sense to have the screen black out while navigating. I will experiment with battery and other settings soon, waiting to be sure what I have is solid and yes, it is.

All of my updates are OTA right from menu. I think the term "dirty flash" is over used. When going from one version to another, i.e.: CM10.2 to CM11 as an OTA update would for sure be "dirty", foolish, and would not work. The gapps alone would not be compatible, much less anything else. Kit Kat came out of nowhere because I had my updates set to ALL, including NIGHTLIES.

I almost made the stupid mistake to just "update" until I realized that the 10 changed to 11 and there was no way possible that one could simply OTA update this release.

So I had to come here and do a lot of reading and ask questions to get prepared for this update, this IS my phone and I cannot afford to lose it by messing around and trying to learn while I go.

Early in the development of Kit Kat, any attempt to update OTA was "a dirty flash" because we are trying something new here. Updates were coming like every 5 minutes, it seemed. These could be real "game changers" like a completely different file system structure, file system permission set, new daemons and obsolete daemons, and a whole bunch of stuff that would simply NOT flash over an existing installation. I think by now you have the nuts and bolts of CM11 pretty much down solid. Lots of work to do with features, getting rid of bugs, enhancements, making Trebuchet the beauty it once was, etc. So, since way last month when I bit the bullet, wiped all of my backups, and installed clean; CM11 and gapps ONLY, did I get a good, solid working system. Previously I just reverted to a working at that time backup and tried to update from there, only to find app crashes, system lockups, and just about anything unpredictable happening at the worst times. All because I did not want to start from scratch, entering all of my accounts again, installing my apps again, setting up and configuring apps that require log ins and passwords, etc. All of my previous "solid backups" came from the days when flashing patches and jbx were pretty much a requirement if you wanted a good, working phone. I do miss the ability to overclock from 1,200 MHz to 1,300MHz, only JBX gave me that option, but a new kernel itself would include a massive new world of issues that could go wrong and complicate troubleshooting should something go wrong so I don't install it anymore. At least for now.

But I tell you what, that clean install really stopped all that crap and I am firmly on solid ground. I even went so far as to delete the rom slot1 and recreate it to get rid of EVERYTHING prior to flashing. I bumped up every space setting by one to give me a little extra "elbow room" because I was constantly having space problems.

NOTE:

ALL OTA updates automatically DO wipe the dalvik and cache. There is nothing "dirty" about an OTA update, it does what it is supposed to. Wipe the cache and dalvik, flash the update, and if necessary (I don't know for sure because I am not a software developer.), wipe the cache and dalvik again prior to rebooting. Anytime the dalvik is wiped, you will see the classic "Android is updating xx out of xxx apps." What that means in plain English is that the dalvik cache is being rebuilt, not simply using the existing dalvik because it would not work or cause serious problems. We need a new one everytime we flash an update.

Okay, maybe this feedback is not helping you further to get problems solved, but positive feedback, IMHO, is just as important as problem feedback. It tells the developer that his work is good. Either the user is lacking something by not installing over a clean, recent install, is using apps or kernels that are not fully supported, or have foreign carriers that add another layer of complication to your issue of the radio and modem.

But for me, I can give you nothing but praise. 3 hours ago I noticed my signal bars down from 5 to 2 bars. Uh oh, time to fire up Cat Log for Stargo, but within 10-20 seconds, I was right back up to 5 bars. Some areas are weak in signal strength so this is normal.

Sugesstion:

Maybe it would be wise when questioning someone with problems to tell you what build they are on, approximately how many updates did they apply since the initial flash of CM11, and to see if they installed clean, fairly recently, recent enough to start with a known good, stable build by the developers. The install should be done on a completely clean slot, either by wiping the crap out of it a few times, or better yet, deleting it and recreating it. I am talking about a build where everything works, should not have issues with normal operation, not stuff like "Still working on Trebuchet" or other cosmetic or new feature releases. You cannot build a house on sand and you cannot build CM11 on a landfill. Make sure they are building on bedrock and have installed CM11 recently enough to start out with a stable build and NO extra layers of complexity like the JBX kernel or other system altering apps or flashes.

Thanks Micheal. I really do love this phone, your efforts to make it stable, and your interest in helping others. It is time somebody stood up to tell you that yes, it does work and it does work quite well in areas that are well covered by their carriers.

"Dirty Micheal"? What does that mean? Don't tell my that you are like me and almost every guy I know who secretly once in a while looks at porn! <gasp!> :eek:

Take care my friend.