I'm back to report. It seems the speaker *volume* issue may be related to Handcent. I installed GO SMS. It's OK, I'm sure it's a fine app once I get used to it and get it tweaked in (I was on Handcent from about 2008, so pretty used to it). My custom tones play at (or very near) full volume on GO SMS, but the speaker continues to sound as though it's struggling. There is distortion which was not present on GB. If I was still using my original Razr, I'd suspect that the speaker could have failed over time, but this damnable CLN replacement should be good, right? The problem started on my first Razr when I installed the ICS update, so I'm suspecting ICS. It doesn't mean I'm necessarily right, but it's my inclination. I had planned on having a chat with someone from Motorola's tech team this evening, but alas, they are located in the UK, and only available 9am to 4pm their time, which severely limits the window of opportunity for me to get in touch. In other news, the purple "candy coating" is starting to flake off my wife's purple Razr, and she's about as mad as a one-legged waitress working at the IHOP. My haptic feedback is also wonky when I'm writing a text. I get the feedback on the first several characters, and then it just stops. And, although I may be alone in this, I rather miss auto-correct, as I have large fingers. I just tried to call my voicemail to check the speaker phone on a whim, and discovered that I cannot make nor receive calls for no apparent reason. Texts and internet are fine. It just keeps getting better and better. Edit: the inability to place or receive calls was related to a setting apparently to do with the LTE ON/OFF app. *sigh*
Last edited by angryquaker; 08-07-2012 at 10:52 PM.
Another update with some information which may be of use to others, and some venting. I found the auto-correct setting shortly after posting about it. Felt like a bonehead. Anyhoo, Motorola does have US-based support. For some reason, when I went to their website it thought I was in Great Britain. There's a very small icon in the lower right-hand corner of their site to change your location, easy to miss if you're not looking for it. I changed it to USA, and voila. Chatted with their tech support (available 9am to 8pm CST), who recommended sending our phones in for repair. It's free of charge, but usually takes 5-7 business days plus transit time to/from wherever their repair center is located. He also suggested that Verizon may provide a "loaner" phone while yours in "in the shop." I'm still not sure how we're going to proceed from here. It is quite discouraging to receive CLN replacement phones after paying for full coverage insurance, and being well within warranty, only to have said CLN devices also exhibit unexpected behavior. It is discouraging to have the manufacturer suggest sending in said CLN replacement devices for repair. Logic would dictate that the replacement devices have been to the repair facility already. Wouldn't one think that's where they're restored to "Like-New" condition? I've had this one less than a week. I understand that the majority of Razr users don't have issues, but it is frustrating that we've had issues with five (5) Razrs at this point. I rather enjoy tweaking and customizing, but I grow weary of Factory Data Resets, and it seems completely counter-intuitive that the manufacturer would suggest I should need to do so on a device which they've supposedly restored to like-new condition. I'm off work today, so I may try starting back at square one, I may also try the leaked .215 update. I just don't know at this point.
Angryquacker, that is extremely frustrating. It's hard to know what your best option is, sending it in for repair or just having Verizon send you another replacement. There are stories of many getting several replacements and finally getting one that is perfect. On the other hand, there is the possibility that motorola will fix it better than a replacement. I am not sure what their track record is on repair but someone may chime in on their experience. I'll keep my fingers crossed for you.
Sent from my DROID RAZR Maxx using Droid Forums
As I mentioned, it seems completely counter-intuitive to me to FDR a new phone, or a CLN phone for that matter. However, after reading yet another post suggesting doing so to a brand spanking new Razr, I'm game. I have my original "new" Razr charging to full now. It's already wiped, so I think I'm going to load up the .215 leak, activate it, then FDR twice, as suggested in another thread. I'm still apprehensive about all this CLN foofaraw, so I'll try it with the one I know was brand new and in the original box. If that doesn't do the trick, maybe I'll send one in for repair. My wife, on the other hand, is about ready to drop Verizon and get an iPhone or something crazy. I'll bring her around if I can get mine straightened out. I still feel that I shouldn't *have* to do a bunch of work to get it working right, but I can, and I also like to think I'm a good sport. So I'll give it the old college try. My name is Russ, btw. You can just call me Russ, or Angry, or Quaker, or what have you. I'm not really angry as a matter of course, nor am I a Quaker, but that's a story for another time...
I agree with you, Russ... it does not make sense to do an fdr and a clnr because it should have been clean when you got it. There was a story on here sometime back that a person got a replacement and it still had the previous owners stuff on it. I imagine that is a rare event but you have to wonder. Hopefully for you (and you wife), you get it working like a charm. It would be great if your new one came through for you and you can send their clnr back.
Sent from my DROID RAZR Maxx using Droid Forums
So...I have .215 running on my original brand new (in Feb) Razr. Oddly enough, the speaker doesn't sound distorted anymore, but I haven't really listened to anything but the volume up/down beep thingy. I did something stupid or something quirked along the way, as Voodoo OTA doesn't seem to be restoring root. It keeps popping up that it "has been granted superuser permissions for an interactive shell," but it's not doing it's thing. It says "/system supports root protection," and "Protected su copy available," but it freezes, and I get a popup that it's not responding, wait, report, or FC. #SU says there is no SU binary installed, and SuperSU cannot install it. Most peculiar. I'll keep kicking it around for a bit.
Ran the DroidRazrRoot.com_ICS utility thing again, and presto! Root restored. I guess that works on the .215 leak. The bad news: either my SD card is fritzed or something went sideways there, too, as my backup is non-existent. The good news: contacts and such are intact thru Google, and I didnt have a big honkin' list of apps since I'd gotten the CLN phone last week. Everything on my SD card is backed up on the 'puter, so that's fine, too. I'm rather surprised the speaker sounds OK now, and I'm pretty stoked about that. Befuddled, but stoked nonetheless. I'll get my junk all situated again and report my findings tomorrow or this weekend. I should go on to bed now, but I'll more likely sit here DLing apps and such, a tweaking. I thank you all for your ongoing support.